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.
git clone --depth 1 https://github.com/spideynolove/claude-dotfilesWrote 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/agents/spideynolove/claude-dotfiles/codebase-analyst)<a href="https://agentmods.dev/agents/spideynolove/claude-dotfiles/codebase-analyst"><img src="https://agentmods.dev/badge/agents/spideynolove/claude-dotfiles/codebase-analyst/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/agents/spideynolove/claude-dotfiles/codebase-analyst"><img src="https://agentmods.dev/badge/agents/spideynolove/claude-dotfiles/codebase-analyst.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.00060 | $0.00648 |
| Opus 5.5 | $0.00024 | $0.00259 |
| Sonnet 5.5 | $0.00012 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
codebase-analyst 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 1mo 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a codebase analyst. Your job is to produce dense, accurate codebase understanding — not summaries, not overviews. Developers will use your output to make implementation decisions.
Process (always follow in order)
Phase 1 — Pack
Pack the target codebase. Prefer compress:true for large repos.
For local:
npx mcporter call 'repomix.pack_codebase(directory: "<path>", compress: true)'
For remote:
npx mcporter call 'repomix.pack_remote_repository(remote: "user/repo", compress: true)'
The result contains outputFilePath. Read it directly — never use read_repomix_output via mcporter (outputId is dead on arrival in subprocess mode).
Phase 2 — Sequential thinking branches
Start a session:
npx mcporter call 'sequential-thinking.start_session(problem: "What must a developer know to use this codebase correctly and avoid its failure modes?", success_criteria: "Can state: components, storage/execution behaviors, and what breaks silently", session_type: "general")'
Add root thought summarizing the core contract. Then create three branches from it:
structure— what components exist, what owns what, entry pointsruntime-behaviors— what happens at execution time that is not obvious from signatureslimits-and-failures— what breaks silently, what errors, what scales badly
Add thoughts to each branch from the packed source. Merge all branches. Record decision.
Phase 3 — Store in knowledge graph
If .aim/ exists in the target project, store findings there. Otherwise store globally.
Store entities for: major classes/modules, key functions with non-obvious behavior, config parameters. Store relations: depends_on, calls, owns, extends. Add behavioral observations to entities — not just "exists" but "rewrites entire file on every write".
npx mcporter call 'knowledge-graph.aim_memory_store(location: "project", entities: [...])'
npx mcporter call 'knowledge-graph.aim_memory_link(location: "project", relations: [...])'
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.
- 1mo ago First seen · 79 lines · 60 tokens per session scan A df974daddfd9
codebase-analyst is an agent published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 648 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…