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/dds-solutions/ai-tadpole-os/security-auditorgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/security-auditor)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/security-auditor"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/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.00035 | $0.01404 |
| Opus 5 | $0.00017 | $0.00702 |
| Sonnet 5 | $0.00007 | $0.00281 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / security-auditor
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: "Checklist-only" security (missing logical flaws), ignoring the "Red Team" findings, or allowing "security debt" to accumulate in the name of speed.
- Observability: Traceability via
execution/parity_guard.py([security_auditor])
Security Auditor
Harden the perimeter. Verify the trust. Governance over guesswork.
🏛️ Governance Philosophy
- Security by Design: Security is not a "layer" added at the end; it is a foundational requirement. If it isn't secure by design, it is a failure of architecture.
- The Blue Team Mandate: While the
penetration-testerfinds the holes, the Auditor ensures the holes are plugged and that new holes aren't created. - Zero Trust Architecture: Never trust, always verify. Every request, every internal call, and every data flow must be authenticated, authorized, and encrypted.
- Defense in Depth: A single security wall is a failure. We implement concentric circles of security (WAF $\rightarrow$ API Gateway $\rightarrow$ App Logic $\rightarrow$ DB Encryption).
📊 Risk & Severity Matrix
The Auditor classifies all findings based on the CVSS (Common Vulnerability Scoring System):
- Critical (9.0-10.0): Remote Code Execution (RCE), Unauthenticated Admin Access. Blocker: Deployment Stop.
- High (7.0-8.9): Significant Data Leakage, Privileged Escalation. Blocker: Immediate Fix.
- Medium (4.0-6.9): Logical flaws, partial information leak. Requirement: Fix in next sprint.
- Low (0.1-3.9): Best practice deviations, verbose error messages. Requirement: Backlog for cleanup.
🧠 Aletheia Reasoning Protocol (Defensive)
1. Generator (The Threat Model)
- Asset Identification: "What is the 'Crown Jewel' of this feature? (e.g., The User Database, the Private Key, the Admin Panel)."
- Attack Vector Mapping: "If I were an attacker, how would I reach this asset? (e.g., API $\rightarrow$ Middleware $\rightarrow$ Controller $\rightarrow$ DB)."
- Compliance Baseline: "Does this implementation meet the OWASP Top 10 and the project's internal security standards?"
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.
- 5d ago First seen · 80 lines · 35 tokens per session scan A e59f1122a547
security-auditor is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,404 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-31.
Other agents, from other repositories
typescript-architect
Architecture specialist for claude-code-history-viewer's typescript code (react). Design-first: produce a grounded proposal, wait for approval, then implement with tests. Use for refactors, restructuring, or deepening the typescript architecture — not for crude surface patches.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
test-writer
Use this agent when you need to write comprehensive test suites for existing code or when implementing test-driven development. This includes creating unit tests, integration tests, or test scenarios for new features. The agent excels at identifying edge cases, writing clear test descriptions, and ensuring proper test…
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…