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/madappgang/magus/securitygit clone --depth 1 https://github.com/MadAppGang/magusWhat 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.00027 | $0.00303 |
| Opus 5 | $0.00014 | $0.00151 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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.
What it actually says
<user_request>$ARGUMENTS</user_request>
- Read
skills/security/SKILL.mdin full first, resolved against this plugin's own directory (the tree this command was loaded from). It is the router: it names which files inskills/security/references/your task actually needs. Read those too before writing code.
Use this for auth, passwords, tokens, injection, rate limiting, CORS, security headers, secrets handling, or a general security review.
- Copy
skills/security/assets/security/into the project. The policy is where the bugs live: two different hashing costs (argon2 for passwords, SHA-256 for tokens), constant-time comparison that survives length mismatch, and a rate-limit key that cannot be forged. - Two measured traps:
bun:sqlitewithout{ strict: true }returns[]for a misspelled parameter instead of throwing; and an unguarded login leaks user existence through timing. - Before reporting done:
bun auditclean, the five greps in the skill's Acceptance section return nothing, and authorisation is checked per resource, not just per route.
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 · 23 lines · 27 tokens per session scan A b08217f6aa1c
security is a command published in the GitHub repository MadAppGang/magus (9 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 303 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-31.
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.