Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add arcasilesgroup/ai-engineering --skill security-auditgit clone --depth 1 https://github.com/arcasilesgroup/ai-engineeringWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/arcasilesgroup/ai-engineering/security-audit)<a href="https://agentmods.dev/skills/arcasilesgroup/ai-engineering/security-audit"><img src="https://agentmods.dev/badge/skills/arcasilesgroup/ai-engineering/security-audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/arcasilesgroup/ai-engineering/security-audit"><img src="https://agentmods.dev/badge/skills/arcasilesgroup/ai-engineering/security-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00081 | $0.02012 |
| Opus 5.5 | $0.00032 | $0.00805 |
| Sonnet 5.5 | $0.00016 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
security-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security audit
Find issues an attacker could actually exploit. The unit of work is a trace: attacker-controlled input → the path it travels → the dangerous sink it reaches. A finding without that trace is a guess.
Read .claude/review/CONVENTIONS.md first — stack detection, scope, severity,
false-positive gate, report format, and the installed-version rule. That last
one matters here more than anywhere: frameworks change their security defaults
between versions, and half of what a reviewer "knows" about a framework's
escaping, CSRF, or cookie behavior is version-specific. Verify against the
installed source before reporting a missing protection the framework provides
by default — or an assumed protection it does not provide.
This is defensive review of code the user owns. Report vulnerabilities with enough detail to fix them — the trace and the fix, not a weaponized exploit.
1. Map the trust boundaries for this stack
Before judging anything, write down which side of the wire each thing lives on. The boundaries differ by architecture, so derive them rather than assuming:
- Untrusted — request bodies, query and path params, headers, cookies, form data, uploaded files, webhook payloads, message-queue contents, and anything from a third-party API. Also: anything a client can set that the server later trusts.
- Server-only — code paths that never ship to a client, and the secrets they read.
- Public — everything reachable from the client bundle or a downloadable artifact, every environment variable exposed by the framework's public-variable convention, and any config baked into a build. All of it is readable by anyone, regardless of whether it is obvious in the UI.
Identify the framework's specific mechanism for each: how it marks a module as server-only, which env-var prefix it inlines into client builds, and where its request-handling boundary sits. Get these from the installed docs or source.
2. Enumerate the attack surface
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed fbb58fca9953
- 1mo ago First seen · 170 lines · 81 tokens per session scan A 0e9490478d37
security-audit is a skill published in the GitHub repository arcasilesgroup/ai-engineering (61 stars, last pushed 2d ago), licensed Apache-2.0. It adds 81 tokens to every session and 2,012 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-12.
Other skills, from other repositories
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
322-frameworks-spring-boot-testing-integration-tests
Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code…
setup-husky-dotnet
Use when configuring Git hooks in .NET projects before team commits occur, to enforce commit message standards and code formatting automatically.
314-frameworks-spring-kafka
Use when you need to design or implement Kafka messaging in Spring Boot — including topic design, producer/consumer implementation, JSON serialization with Boot factory customizers, Testcontainers @ServiceConnection integration tests, retries and dead-letter topics, idempotency, and error handling. This should trigger…
audit
Independent, on-demand AL codebase auditor for Business Central. Judges the code against BCQuality (citable knowledge) plus native checks for what BCQuality does not reach. Read-only; advisory verdict. Default scope: objects changed vs main; full codebase on request.
review
WCAG 2.2 AA curated accessibility review — distinguishes automatically detectable, browser-assisted, and manual/human-judgment findings with evidence citations and SC mapping. Composes with design-assessment/design-improvement/frontend-design-review.