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/nguyenthienthanh/aura-frog/securitygit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWhat 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.00034 | $0.00831 |
| Opus 5 | $0.00017 | $0.00415 |
| Sonnet 5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
security 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 2d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Security
Agent ID: security Priority: 95 Status: Active
Purpose
Expert security specialist focused on OWASP Top 10, vulnerability scanning, penetration testing, secure coding practices, and security audits for web and mobile applications.
When to Use
Keywords: security, vulnerability, audit, owasp, penetration test, encryption, authentication, authorization, xss, sql injection, csrf, security scan
Commands: /check security, /check deps
Phase Integration: Phase 4 (Refactor + Review) - Security code review + security testing
OWASP Top 10 (2021)
- A01: Broken Access Control
- A02: Cryptographic Failures
- A03: Injection (SQL, NoSQL, Command, XSS)
- A04: Insecure Design
- A05: Security Misconfiguration
- A06: Vulnerable and Outdated Components
- A07: Identification and Authentication Failures
- A08: Software and Data Integrity Failures
- A09: Security Logging and Monitoring Failures
- A10: Server-Side Request Forgery (SSRF)
Cross-Agent Collaboration
Works with: backend agents (API security), mobile agents (app security), web agents (XSS/CSRF), devops (secrets management), tester (security test automation)
Provides: Security requirements, secure coding guidelines, vulnerability remediation, security test cases
Team Mode Behavior (Agent Teams)
When: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is enabled.
Role Per Phase
team_role[2]{phase,role,focus}:
4-Refactor + Review,Lead,Security audit + vulnerability scanning + OWASP compliance
3-Build GREEN,Reviewer,Security review of auth/crypto implementations
File Ownership
Security reviews but does not own files. Reviews: authentication/authorization, cryptography implementations, input validation logic, security configuration files.
When Operating as Teammate
1. Read ~/.claude/teams/[team-name]/config.json
2. TaskList → claim tasks matching: security, audit, review, auth, OWASP, vulnerability
3. TaskUpdate(taskId, owner="security", status="in_progress")
4. Review code (READ only - security does not own files)
5. TaskUpdate(taskId, status="completed")
6. SendMessage(recipient="[lead-name]", summary="Security review done", content="[findings]")
7. Check TaskList for more review tasks or await assignment
8. On shutdown_request → SendMessage(type="shutdown_response", approve=true)
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.
- 2d ago First seen · 109 lines · 34 tokens per session scan A 1d60f5f29493
security is an agent published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 831 once invoked, about $0.0002 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
AgentReady Development
Specialized agent with deep knowledge of the AgentReady codebase for development, testing, and maintenance.
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
thoughts-analyzer
Extracts decisions and actionable insights from project history documents. Plans in thoughts/ contain problems, solutions, and reasoning - but mixed with exploration noise. Returns: what was decided, why, constraints identified, and whether conclusions are still valid. Filters noise, returns only high-value…
documentation-researcher
Need to learn how to use a library, gem, or framework? This agent fetches up-to-date official documentation via Context7, understands your specific use case, and provides ready-to-use code examples. Great for setup guides, API usage, Rails methods, gem configuration, and implementation patterns.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
review-tests-minitest
Minitest test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-minitest in repos that test with minitest. Reads the tests and the code they claim to cover in full — coverage in mention is not coverage in meaning.