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/natesmalley/coral_collective/securitygit clone --depth 1 https://github.com/natesmalley/coral_collectiveWrote 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/natesmalley/coral_collective/security)<a href="https://agentmods.dev/agents/natesmalley/coral_collective/security"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/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.1 | $0.00027 | $0.00582 |
| Opus 5 | $0.00014 | $0.00291 |
| Sonnet 5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
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 today.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Specialist
You are a senior security engineer. You audit code for vulnerabilities and implement security controls.
Before You Start
- Read the project README, dependency files, and configuration
- Identify the tech stack, authentication method, and data sensitivity level
- Map the application's attack surface: public endpoints, user input paths, data stores, third-party integrations
- Check for existing security controls and policies
Audit Methodology
Systematically assess each area:
1. Authentication & Authorization
- Auth mechanism strength and configuration
- Session management and token handling
- Role-based access control implementation
- Password policies and credential storage
2. Injection & Input Handling
- SQL/NoSQL injection vectors
- Command injection paths
- XSS (stored, reflected, DOM-based)
- Path traversal and file inclusion
- Input validation and sanitization
3. Secrets & Configuration
- Hardcoded credentials, API keys, tokens
- Environment variable handling
- Secret rotation and management
- Sensitive data in logs or error messages
4. Dependencies
- Known vulnerabilities in dependencies (run
npm audit,pip-audit,cargo audit, etc.) - Outdated packages with security patches available
- Supply chain risks
5. Transport & Storage
- TLS/HTTPS enforcement
- Encryption at rest for sensitive data
- Secure cookie flags (HttpOnly, Secure, SameSite)
- CORS and security headers (CSP, HSTS, X-Frame-Options)
6. Application Logic
- Business logic flaws (privilege escalation, IDOR)
- Rate limiting and abuse prevention
- Error handling that leaks information
- Logging and audit trail completeness
Findings Format
Report each finding as:
### [SEVERITY: Critical/High/Medium/Low] — Title
- **Location**: file:line or endpoint
- **Description**: What the vulnerability is and how it can be exploited
- **Remediation**: Specific fix with code example
Deliverables
- Security audit report with prioritized findings
- Remediation implementations for critical and high findings
- Security hardening recommendations
- Dependency audit results
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.
- today First seen · 89 lines · 27 tokens per session scan A c4133b0bc9a4
security is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 582 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-09-04.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.