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 skills add doancan/mags --skill mags-statusgit clone --depth 1 https://github.com/doancan/magsWrote 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/doancan/mags/mags-status)<a href="https://agentmods.dev/skills/doancan/mags/mags-status"><img src="https://agentmods.dev/badge/skills/doancan/mags/mags-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/doancan/mags/mags-status"><img src="https://agentmods.dev/badge/skills/doancan/mags/mags-status.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00400 |
| Opus 5 | $0.00009 | $0.00200 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
mags-status 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 8d 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
MAGS Status
Display a comprehensive project status dashboard.
Steps
1. Gather data
Call these in parallel:
mags_project_summary— Get overall project summarymags_validate_docs— Check documentation healthmags_recallwith query "recent decisions and blockers" — Surface relevant memories
2. Format the dashboard
Present the output as a clean dashboard. Use this format:
== MAGS Project Status ==
PROJECT
Name: <project name>
Stack: <tech stack>
State: <project state>
DOCUMENTATION HEALTH
Total docs: <N>
Valid: <N> ok
Warnings: <N> (list brief reasons)
Errors: <N> (list brief reasons)
RECENT MEMORY
- <any recalled decisions or notes>
NEXT STEPS
1. <recommended action>
2. <recommended action>
3. <recommended action>
3. Offer actions
After displaying the dashboard, say:
"Run /mags-docs-validate to fix doc issues, or use mags_remember to save important decisions."
Do not take any further action unless the user asks.
Related commands:
| Command | Description |
|---|---|
/mags-help |
See all available commands |
/mags-docs-validate |
Check documentation health in detail |
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.
- 8d ago First seen · 67 lines · 17 tokens per session scan A a52a4f18506b
mags-status is a skill published in the GitHub repository doancan/mags (3 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 400 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 skills, from other repositories
resume
Read-only ORIENTATION. It reads the current git branch, finds the branch's active run in mneme's event log, reconstructs the phase map (closed / ready / blocked / paused-on-boundary) plus the staged-but-unaccepted notes, and SUGGESTS the /mneme:dev continuation in REAL syntax — slug + until, with boundary candidates…
promote-idea
Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".
vendor-management
Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…
recap-doc
Post-development recap document generator. Use when: AI/Codex has implemented a feature and the user needs a guided walkthrough of what changed and why, with blind-spot detection and anticipated questions. Not for: Q&A follow-up (use /recap-ask), technical share-out for teammates (use /tech-brief), or generic code…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this…
ledger
OPS on-demand: This skill should be used when the user asks to "ops ledger", "what did we handle", or…