Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MacroMan5/macromanatlasnpx agentmods add skills/macroman5/macromanatlas/index-initWrote 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-init)<a href="https://agentmods.dev/skills/macroman5/macromanatlas/index-init"><img src="https://agentmods.dev/badge/skills/macroman5/macromanatlas/index-init.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.00036 | $0.01791 |
| Opus 5 | $0.00018 | $0.00896 |
| Sonnet 5 | $0.00007 | $0.00358 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
index-init 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/index-init
Generate a complete project index with per-module README files.
Step 1: Announce
Say: "I'm using the index-init skill to generate a project index."
Step 2: Detect project type
Glob the root directory for these signals. Use first match wins priority:
| Priority | Signal | Type | Module detection |
|---|---|---|---|
| 1 | CMakeLists.txt containing add_subdirectory() |
cpp-cmake | Each add_subdirectory() argument = module |
| 2 | Cargo.toml containing [workspace] |
rust-cargo | Each members entry = crate |
| 3 | go.work or multiple go.mod |
go | Each use directive or go.mod directory = module |
| 4 | package.json containing "workspaces" |
node-workspaces | Each workspace pattern match = package |
| 5 | *.sln file |
dotnet | Each .csproj referenced = project |
| 6 | pom.xml containing <modules> |
java-maven | Each <module> = subproject |
| 7 | build.gradle or settings.gradle containing include |
java-gradle | Each include(':...') = subproject |
| 8 | pyproject.toml or setup.py |
python | Packages or top-level dirs with __init__.py |
| 9 | pubspec.yaml |
dart-flutter | Top-level or packages/ dirs |
| 10 | Fallback | generic | Top-level dirs containing source files (.cpp, .py, .js, .ts, .rs, .go, .java, .cs, .dart) |
For each detected type, extract:
- Modules: from build/manifest files as described above
- Purpose: from comments, description fields, docstrings, existing README content
- Dependencies: from link directives (
target_link_libraries), imports, manifest deps - Public API: from interface files (I*.h), exports, pub functions — names + method signatures only
- Files: use
git ls-files(respects .gitignore) to list source + config files per module. Fallback to Glob if not a git repo.
Never index: .env, .env.*, .git/, *.key, *.pem, .npmrc, .pypirc, .aws/, .ssh/, *credentials*, *secret*, *token*, binary blobs (images, compiled objects, archives).
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 · 183 lines · 36 tokens per session scan A 2671b5cb7bb0
index-init is a skill published in the GitHub repository MacroMan5/macromanatlas (3 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,791 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.
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…
explain
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do…
spike
A time-limited research task for answering an open technical or product question before implementation begins.