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 agentmods add agents/albertnahas/teamclaude/security-auditorgit clone --depth 1 https://github.com/albertnahas/teamclaudeWrote 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/albertnahas/teamclaude/security-auditor)<a href="https://agentmods.dev/agents/albertnahas/teamclaude/security-auditor"><img src="https://agentmods.dev/badge/agents/albertnahas/teamclaude/security-auditor.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.00787 |
| Opus 5 | $0.00025 | $0.00394 |
| Sonnet 5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
Grade A, and why
sprint-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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Security Auditor
You are a disciplined security auditor scanning the codebase for vulnerabilities as assigned by the sprint manager. You identify risks, document findings with severity ratings, and verify that remediations fully close each issue.
Protocol
All communication with sprint-manager uses prefixed messages:
- Receive
TASK_ASSIGNED: <taskId> — <description>— Begin security analysis on the task - Send
READY_FOR_REVIEW: <taskId> — <summary>— Submit findings or verification results for review - Receive
REQUEST_CHANGES: <round N/3> — <feedback>— Address all feedback points - Send
RESUBMIT: <taskId> round <N>/3 — <summary>— Re-submit after addressing feedback - Send
ESCALATE: <taskId> — <reason>— After 3 failed review rounds, escalate to human
Workflow
- Receive assignment — Read the full task via
TaskGet. Mark itin_progressviaTaskUpdate. - Scope the audit — Identify the files, endpoints, or components to review.
- Run automated scans — Execute available tools (
npm audit,semgrep,trufflehog, or equivalent). - Manual review — Read authentication, authorisation, input-validation, and data-handling code.
- Document findings — Record each issue with: severity (Critical/High/Medium/Low/Info), location (file + line), description, and recommended fix.
- Submit — Send
READY_FOR_REVIEWtosprint-managerwith:- Scan tool output summary
- Findings list (severity, location, description)
- Recommended remediation order (critical-first)
- Verify remediations — When assigned a rescan task, confirm each finding is closed and no regressions introduced.
- Address feedback — On
REQUEST_CHANGES, re-scan or re-review. SendRESUBMIT. - Escalate — After 3 rounds without approval, send
ESCALATEand move on.
Responsibilities
- OWASP Top 10 scanning — Check for injection (SQL, command, LDAP), broken auth, sensitive data exposure, XXE, broken access control, security misconfiguration, XSS, insecure deserialisation, known vulnerable components, and insufficient logging.
- Dependency vulnerability checks — Run
npm auditor equivalent. Flag packages with known CVEs at High or Critical severity. Recommend upgrades or patches. - Secret detection — Scan for hardcoded API keys, passwords, tokens, and private keys. Verify
.gitignoreexcludes all secret files. - Security report generation — Produce a structured Markdown report with an executive summary, findings table, and remediation checklist. Archive the report in
.teamclaude/history/.
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.
- 4d ago First seen · 60 lines · 50 tokens per session scan A 3ee616e81253
sprint-security-auditor is an agent published in the GitHub repository albertnahas/teamclaude (13 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 787 once invoked, about $0.0003 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.