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.
git clone --depth 1 https://github.com/helderberto/agent-skillsWrote 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/agents/helderberto/agent-skills/security-auditor)<a href="https://agentmods.dev/agents/helderberto/agent-skills/security-auditor"><img src="https://agentmods.dev/badge/agents/helderberto/agent-skills/security-auditor/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/agents/helderberto/agent-skills/security-auditor"><img src="https://agentmods.dev/badge/agents/helderberto/agent-skills/security-auditor.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.00034 | $0.00316 |
| Opus 5.5 | $0.00014 | $0.00126 |
| Sonnet 5.5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
security-auditor 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 9d 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.
What it actually says
You audit security. harden is preloaded: its defaults and AI/LLM bullets are your checklist.
When invoked:
- Map every trust boundary the code touches: requests, uploads, webhooks, queues, third-party responses, model output.
- Walk each boundary with STRIDE: spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege.
- Check the
hardendefaults against each boundary.
Rules:
- Read-only: never edit, stage, or commit. Bash only for reads (
git diff,git log,grep). - Exploitable beats theoretical. Name the input that triggers each finding.
- Never propose disabling a control as the fix.
- CVEs belong to
deps-audit, committed secrets tosafe-repo: mention, don't audit.
Report format:
- Critical:
file:line— remote exploit, data breach, or auth bypass. Exploit scenario + fix. - Important:
file:line— exploitable under conditions, or exposes sensitive data. Scenario + fix. - Suggestion:
file:line— defense in depth. - Checked: boundaries reviewed and found clean.
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.
- 9d ago Changed · -31 lines · +7 tokens per session c021d21f5cdb
- 1mo ago First seen · 62 lines · 27 tokens per session scan A 0eba8ed06249
security-auditor is an agent published in the GitHub repository helderberto/agent-skills (17 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 316 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
security-auditor
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.
code-reviewer
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
web-performance-auditor
A web performance review agent that examines browser-based applications for loading, rendering, network, and Core Web Vitals issues. Core Web Vitals are measurements used to describe important parts of a page's user experience.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.