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 MacroMan5/macromanatlas --skill index-statusgit clone --depth 1 https://github.com/MacroMan5/macromanatlasWrote 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/macroman5/macromanatlas/index-status)<a href="https://agentmods.dev/skills/macroman5/macromanatlas/index-status"><img src="https://agentmods.dev/badge/skills/macroman5/macromanatlas/index-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/macroman5/macromanatlas/index-status"><img src="https://agentmods.dev/badge/skills/macroman5/macromanatlas/index-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.00033 | $0.00602 |
| Opus 5 | $0.00016 | $0.00301 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
index-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 10d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/index-status
Show the health and status of the project index.
Step 1: Announce
Say: "Checking MacroManAtlas index status..."
Step 2: Check index existence
Read .claude/index.md. If it doesn't exist, report:
MacroManAtlas Status
────────────────
⚠ No index found. Run /index-init to generate one.
And stop.
Step 3: Parse index metadata
From .claude/index.md, extract:
- Generation timestamp
- Project type
- Module count
- File count
Step 4: Check each module
For each module listed in the index:
- Check if
<Module>/README.mdexists - Get the README's last modification time (use
git log -1 --format=%ci -- <Module>/README.mdor Bashstat) - Get the latest file modification in the module (use
git log -1 --format=%ci -- <Module>/) - Count files in filesystem:
git ls-files <Module>/ | wc -l(or Glob fallback) - Count files listed in the README's Files table
- Compare: if filesystem has more files than README, mark as stale
Status symbols:
- ✓ = README exists and is fresh (no newer files than README)
- ⚠ = README exists but stale (newer files not indexed)
- ✗ = No README.md found
Step 5: Check hooks
Read the plugin's hooks.json to verify hook registration. Check for:
- SessionStart hook
- PostToolUse hook
- PreCompact hook
- Stop hook
Step 6: Check recent sync activity
Read last 20 lines of ~/.claude/logs/index-sync.log (if exists).
Extract the most recent sync: module name and timestamp.
Step 7: Present dashboard
Format output as:
MacroManAtlas Status
────────────────
Index: .claude/index.md (generated <time ago>)
Type: <project-type> | Modules: <N> | Indexed files: <N>
Module Health:
✓ ModuleName — <N> files, README fresh
⚠ ModuleName — <N> files, README stale (<N> new files not indexed)
✗ ModuleName — no README.md
Hooks: SessionStart ✓ | PostToolUse ✓ | PreCompact ✓ | Stop ✓
Last sync: <module> (<time ago>) — <change_type>
If no sync log exists, show: Last sync: no activity recorded
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.
- 10d ago First seen · 82 lines · 33 tokens per session scan A 324eca19995c
index-status is a skill published in the GitHub repository MacroMan5/macromanatlas (3 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 602 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 skills, from other repositories
root-cause
Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
x-bug2rag
A knowledge-capture tool that turns reusable bug explanations into a local RAG collection, meaning a searchable store of text that an agent can retrieve later. It records the trigger, incorrect implementation, correct implementation, and observable difference.
x-cr
A software-correctness investigation skill for finding why code behaves differently from what was expected. It uses evidence from code paths, specifications, tests, logs, and changes to assess possible causes.
x-fix
A bug-fixing skill with separate paths for directly reported bugs, correctness-review findings, and failed verification or quality-gate reports. It records completed fixes and their validation in project reports.