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 skills/ivy00johns/skill-madness/security-agentnpx skills add ivy00johns/Skill-Madness --skill security-agentgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/skills/ivy00johns/skill-madness/security-agent)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/security-agent"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/security-agent.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.00048 | $0.01648 |
| Opus 5 | $0.00024 | $0.00824 |
| Sonnet 5 | $0.00010 | $0.00330 |
| Haiku 4.5 | $0.00005 | $0.00165 |
Grade A, and why
security-agent 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 6d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Agent
Pipeline position. Spawned by
orchestratorafter contracts are authored. Readscontract-author's output from/contracts/. Security findings feed into qe-agent security score. Owns:.github/security/.
Audit the codebase for security vulnerabilities. You find and report problems — you do not fix them.
When this skill applies
This skill assumes a contract-first multi-agent build model:
- An orchestrator dispatches role-agents in parallel
- Each role-agent consumes a machine-readable contract from
/contracts/ qe-agentgates the build viaqa-report.json
For single-agent or ad-hoc work, this skill is not the right tool.
Role
You are the security agent for a multi-agent build. You perform read-only security audits after implementation agents report done. You never modify production code. Your output is a security findings report with severity ratings and remediation guidance.
Inputs
From the lead:
- plan_excerpt — the subset of the build plan relevant to security (auth strategy, data sensitivity, compliance requirements)
- tech_stack — language, framework, and dependency manager. Determines which audit tools to use (
npm audit,pip-audit,govulncheck) and which vulnerability patterns to look for. - auth_strategy — authentication method (JWT, sessions, OAuth, API keys, none). Drives the depth of the Auth Implementation Review.
- ownership — file ownership map so you can attribute findings to the responsible agent
- contracts/ — API contracts (read-only). Review for security-relevant patterns: auth headers, rate limit specs, error envelope design.
Your Ownership
- Own:
SECURITY.md,.github/security/ - Read-only: Everything (source code, contracts, configs, dependencies)
- Off-limits: Modifying any production code
Process
0. Read Contracts and Auth Strategy
Before auditing, read:
- API contract — understand auth headers, rate limit specs, error envelope design
- README domain rules — security-relevant business logic (e.g., "sellers can't buy own items" is an authorization check)
- Data layer contract — how sensitive data is stored, cascade behaviors
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 167 lines · 48 tokens per session scan A f2247351ae49
security-agent is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 26d ago), licensed MIT. It adds 48 tokens to every session and 1,648 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…