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 commands/ilyasibrahim/claude-agents-coordination/securitygit clone --depth 1 https://github.com/ilyasibrahim/claude-agents-coordinationWrote 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/commands/ilyasibrahim/claude-agents-coordination/security)<a href="https://agentmods.dev/commands/ilyasibrahim/claude-agents-coordination/security"><img src="https://agentmods.dev/badge/commands/ilyasibrahim/claude-agents-coordination/security.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.00014 | $0.00959 |
| Opus 5 | $0.00007 | $0.00479 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
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 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan Command
Invoke security-engineer agent for security analysis.
Usage
/security [path] # Full OWASP scan
/security [path] --threat-model # STRIDE threat modeling
/security [path] --compliance # Compliance review
/security [path] --deps # Dependencies only
Default Mode: Scan
Task(security-engineer, "
Mode: scan
Target: [path or entire codebase]
Perform comprehensive security scan:
1. OWASP Top 10 Check
- Injection (SQL, Command, XSS)
- Broken Authentication
- Sensitive Data Exposure
- XXE
- Broken Access Control
- Security Misconfiguration
- XSS
- Insecure Deserialization
- Vulnerable Components
- Insufficient Logging
2. Input Validation
- All user input entry points
- API parameter handling
- File upload validation
- Query string parsing
3. Authentication/Authorization
- Session management
- Password handling
- Token validation
- Permission checks
4. Secrets Detection
- Hardcoded credentials
- API keys in code
- Private keys
- Connection strings
5. Dependency Vulnerabilities
- Known CVEs
- Outdated packages
- Unmaintained libraries
Output: .claude/reports/security/security-scan-[target]-YYYYMMDD.md
")
Threat Model Mode
/security [feature-description] --threat-model
Task(security-engineer, "
Mode: threat-model
Feature: [description]
Perform STRIDE analysis:
- Spoofing
- Tampering
- Repudiation
- Information Disclosure
- Denial of Service
- Elevation of Privilege
Include:
- Data flow diagram
- Attack surface mapping
- Trust boundaries
- Threat mitigations
Output: .claude/reports/security/threat-model-[feature]-YYYYMMDD.md
")
Compliance Mode
/security [path] --compliance [standard]
Standards: gdpr, soc2, hipaa, pci
Task(security-engineer, "
Mode: compliance
Target: [path]
Standard: [GDPR/SOC2/HIPAA/PCI]
Review compliance with:
- Data handling requirements
- Access control requirements
- Audit logging requirements
- Encryption requirements
Output: .claude/reports/security/compliance-[standard]-YYYYMMDD.md
")
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 · 201 lines · 14 tokens per session scan A c8ec5ad57465
security is a command published in the GitHub repository ilyasibrahim/claude-agents-coordination (83 stars, last pushed 3mo ago), licensed Unlicense. It adds 14 tokens to every session and 959 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.