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-rebuildgit 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-rebuild)<a href="https://agentmods.dev/skills/macroman5/macromanatlas/index-rebuild"><img src="https://agentmods.dev/badge/skills/macroman5/macromanatlas/index-rebuild/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-rebuild"><img src="https://agentmods.dev/badge/skills/macroman5/macromanatlas/index-rebuild.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.00721 |
| Opus 5 | $0.00016 | $0.00360 |
| Sonnet 5 | $0.00007 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
index-rebuild 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 11d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/index-rebuild
Rebuild the project index, optionally targeting a specific module with custom instructions.
Usage
/index-rebuild Full rebuild (all modules + index)
/index-rebuild --module MacroMan-Tracking Rebuild only Tracking README + update index
/index-rebuild --module MacroMan-Tracking --m "Focus on TrackState machine transitions"
Step 1: Parse arguments
Parse $ARGUMENTS for:
--module <name>— target a specific module (optional)--m "<instructions>"or--m <instructions>— custom emphasis instructions (optional)
If no arguments: full rebuild of all modules.
Step 2: Announce
If --module specified:
Say: "Rebuilding index for module: "
If full rebuild:
Say: "Rebuilding complete project index..."
Step 3a: Targeted rebuild (--module specified)
- Verify the module directory exists. If not, list available modules and ask user to pick one.
- Scan the module:
- List files with
git ls-files <module>/(or Glob fallback) - Read interface/header/export files for public API
- Extract dependencies from build files (CMakeLists.txt, package.json, Cargo.toml, etc.)
- Generate tags from file names, class names, function names
- List files with
- Read existing
<Module>/README.md - Preserve the
<!-- CUSTOM -->section content - Regenerate the
<!-- AUTO-GENERATED -->section using the same template as /index-init Step 3 - If
--minstructions provided:- Use them to guide emphasis in the README generation (what classes to detail, what patterns to document)
- Save the instructions in the CUSTOM section as:
**Index instructions**: <instructions>
- Write the updated README
- Update
.claude/index.md:- Update the module's row in the Modules table
- Update the Tag Index for this module's tags only
- Regenerate
.claude/index.summary.mdfrom.claude/index.md(keep under 4KB)
Step 3b: Full rebuild (no --module flag)
Perform the same steps as /index-init Steps 2-4, but:
- PRESERVE all
<!-- CUSTOM -->sections in existing READMEs - PRESERVE the
<!-- CUSTOM -->section in.claude/index.md - Do NOT re-add the CLAUDE.md section if it already exists (look for "Code Navigation" or "Code Index")
- Do NOT modify hooks (they're managed by the plugin)
- Regenerate the "How to Use" section in
.claude/index.mdwith the navigation strategy (tags → README → targeted grep)
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.
- 11d ago First seen · 73 lines · 33 tokens per session scan A 8d4742df82f3
index-rebuild 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 721 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
delegate
Let Claude Architect route a versioned implementation spec through the trusted MCP runtime, independently review the Candidate Artifact, record a decision, and integrate only accepted bytes. Use for implementation delegation, Producer selection, or commitment-boundary review.
codex
Run the Codex CLI directly in the user's checkout for code analysis, refactoring, or automated editing without Claude Architect's verified delegation lifecycle.
commit
A guided process for committing code changes to Git. It checks the working tree, follows a conventional commit format, links a task when available, reviews the changes, and asks for approval.
x-multi-llm-align
A review process in which two sub-agents examine an API, data format, event schema, or workflow from their separate implementation perspectives. The user passes documents and feedback between them over multiple rounds.
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
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.