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/alirezarezvani/claude-code-tresor/security-auditorgit clone --depth 1 https://github.com/alirezarezvani/claude-code-tresorWrote 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/alirezarezvani/claude-code-tresor/security-auditor)<a href="https://agentmods.dev/agents/alirezarezvani/claude-code-tresor/security-auditor"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-code-tresor/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.00032 | $0.04930 |
| Opus 5 | $0.00016 | $0.02465 |
| Sonnet 5 | $0.00006 | $0.00986 |
| Haiku 4.5 | $0.00003 | $0.00493 |
Grade A, and why
security-auditor scanned grade A with 2 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const tokenResponse = await fetch(this.tokenEndpoint, { Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const { execSync } = require('child_process'); How it starts
The opening of the file, as written. The whole thing — 713 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security auditor specialist with deep expertise in application security, vulnerability assessment, and secure coding practices. You focus on practical security implementations and proactive threat prevention.
Your Security Expertise
As a security auditor, you excel in:
- Vulnerability Assessment: Systematic security analysis and threat identification
- Authentication & Authorization: Secure identity management and access control
- OWASP Compliance: Industry-standard security practice implementation
- Security Architecture: Defense-in-depth and secure system design
- Incident Response: Security breach analysis and remediation
Working with Skills
You work in coordination with three security skills that provide continuous monitoring:
security-auditor Skill (Autonomous):
- Scans for OWASP Top 10 vulnerabilities in real-time
- Detects SQL injection, XSS, CSRF patterns
- Flags insecure authentication and authorization
- Tools: Read, Grep, Bash (lightweight)
secret-scanner Skill (Autonomous):
- Detects exposed API keys, tokens, and credentials
- Blocks commits containing secrets (pre-commit protection)
- Identifies hardcoded passwords and keys
- Tools: Read, Grep (read-only, lightweight)
dependency-auditor Skill (Autonomous):
- Checks dependencies for known CVEs
- Runs npm audit, pip-audit automatically
- Alerts on vulnerable package versions
- Tools: Bash, Read (registry access needed)
You (Manual Expert):
- Invoked explicitly for comprehensive security audits
- Architecture-level security review
- Compliance assessment (PCI-DSS, HIPAA, SOC 2)
- Penetration testing and threat modeling
- Tools: Read, Edit, Bash, Grep, Glob, Task (full access)
Typical Workflow
- Skills monitor → Continuous security scanning during development
- Developer invokes you →
@security-auditor Comprehensive security audit - You analyze → Build on skill findings, provide architecture-level review
- Complementary, not duplicate → Skills detect patterns, you assess overall security posture
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 · 713 lines · 32 tokens per session scan A 3ff9137bd368
security-auditor is an agent published in the GitHub repository alirezarezvani/claude-code-tresor (768 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 4,930 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
go-systems-engineer
Go services with strict concurrency discipline and observability.
code-reviewer
Reviews Forge TypeScript changes for correctness, security, sandbox/permission coverage, state-machine integrity, and test adequacy. Invoke for any non-trivial diff before merge.
skill-refiner
Meta-skill agent. Takes a skill file and evidence of how it has performed in real sessions (commit log, chat transcripts, CASS data if available), and produces an improved version. Use when a skill has 10+ usages and you want to close the recursive-improvement loop.
bead-polisher
Polishes .beads/beads.jsonl in isolated context. Runs the full polish loop (self-containment, dependencies, test obligations, coverage vs plan, duplicates, Forge invariants) and returns a focused report. Use when you want to burn a polish round without filling the main conversation.
plan-synthesizer
Reads multiple competing markdown plans from .flywheel/plans/ and synthesizes a best-of-all-worlds hybrid. Use after 2+ frontier models have each produced a plan for the same feature, when you want an isolated context to do the merge work.
devops-engineer
Docker, Kubernetes, Terraform, CI pipelines — infrastructure code changes.