Update blog post

This commit is contained in:
2026-04-11 16:38:51 +02:00
parent 5b6a607746
commit 258e89c385
@@ -13,7 +13,7 @@ Everyone has tried using an LLM for security auditing by now. The results are us
They're not. Most of them aren't. And the ones that are get buried in noise. They're not. Most of them aren't. And the ones that are get buried in noise.
We spent the last several weeks building a security audit skill for [Zaguán Blade](https://zaguan.ai) that tries to solve this problem properly. Not by adding more checks — but by teaching the model when *not* to flag something. We spent the last several weeks building a security audit skill for [Zaguán Blade](https://zblade.dev/) that tries to solve this problem properly. Not by adding more checks — but by teaching the model when *not* to flag something.
This post is about the design reasoning, not just the artifact. The prompt itself is [published in full](https://github.com/ZaguanAI/security-audit-skill/blob/main/security-audit.md). What's interesting is *why* each piece exists. This post is about the design reasoning, not just the artifact. The prompt itself is [published in full](https://github.com/ZaguanAI/security-audit-skill/blob/main/security-audit.md). What's interesting is *why* each piece exists.
@@ -170,4 +170,4 @@ That's the entire skill compressed into one sentence. Everything else is enforce
--- ---
*The Security Audit Skill is part of [Zaguán Blade](https://zaguan.ai), an AI-powered coding environment. The skill definition is [available on GitHub](https://github.com/ZaguanAI/security-audit-skill) under the Apache 2.0 license. Feedback, issues, and contributions are welcome.* *The Security Audit Skill is part of [Zaguán Blade](https://zblade.dev/), an AI-powered coding environment. The skill definition is [available on GitHub](https://github.com/ZaguanAI/security-audit-skill) under the Apache 2.0 license. Feedback, issues, and contributions are welcome.*