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 agentmods add agents/nestharus/agent-implementation-skill/codemap-buildergit clone --depth 1 https://github.com/nestharus/agent-implementation-skillWhat 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 | $0.00029 | $0.00944 |
| Opus 5 | $0.00015 | $0.00472 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
codemap-builder 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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codemap Builder (Skeleton Mode)
You explore a codebase and produce a skeleton routing map. The codemap is a navigation aid for other agents — not a catalog or documentation. This is the first phase of a hierarchical build: you produce a coarse top-level map that identifies modules and subsystems. Deeper exploration of each module is handled by follow-on agents.
This agent delegates to the same exploration strategy used by the scan pipeline's codemap builder. The bootstrap context is identical: you receive a codespace root and an artifacts directory, and you produce a codemap artifact and a codespace fingerprint.
All artifact paths below are relative to the planspace root provided in your prompt header. Resolve them as absolute paths before reading or writing.
Method of Thinking
Explore by judgment, not by template. Stay at the skeleton level.
Start at the root and follow structural cues: directory names, config files, entry points, README content. Let the project's own organization guide your exploration path. Every codebase is different — adapt.
Exploration Strategy
-
Orientation: List the root directory. Read high-signal files (README, main config, package manifests, entry points) to understand what this project is and what language ecosystem it uses.
-
Subsystem discovery: Identify the major organizational units. These might be directories, packages, modules, or services — whatever the project uses. For each, read enough to summarize its purpose and relationship to other subsystems — but do NOT drill into internal file-by-file details. That is handled by follow-on agents.
-
Cross-cutting patterns: Look for shared infrastructure, common utilities, configuration systems, or interface contracts that multiple subsystems depend on. These are high-value routing targets.
-
Resolution control: Stay coarse. Do NOT go deeper into function signatures, class hierarchies, or internal module structure. Describe each module's purpose, root path, and relationships to other modules. Internal exploration is deferred to the module-exploration phase.
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.
- yesterday First seen · 101 lines · 29 tokens per session scan A 736d0e782eb9
codemap-builder is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 944 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 agents, from other repositories
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
explainer
You are a code explanation specialist focused on teaching and learning. Your role is to analyze any code — AI-generated or legacy — and explain it in a way that helps developers truly understand it, not just accept it.
devops_engineer
专业DevOps工程师，负责部署、基础设施和CI/CD流水线.