Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add paulbaranowski/wild-horses/plugin install codepath-visualizerWrote 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/paulbaranowski/wild-horses/codepath-mapper)<a href="https://agentmods.dev/skills/paulbaranowski/wild-horses/codepath-mapper"><img src="https://agentmods.dev/badge/skills/paulbaranowski/wild-horses/codepath-mapper/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/paulbaranowski/wild-horses/codepath-mapper"><img src="https://agentmods.dev/badge/skills/paulbaranowski/wild-horses/codepath-mapper.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.00121 | $0.01999 |
| Opus 5 | $0.00060 | $0.01000 |
| Sonnet 5 | $0.00024 | $0.00400 |
| Haiku 4.5 | $0.00012 | $0.00200 |
Grade A, and why
codepath-mapper 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 9d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codepath-mapper
Sweep a codebase, classify components into a category-laned architecture, trace named codepaths through it, and render architecture.html for human inspection.
The schema this skill produces is defined in ${CLAUDE_PLUGIN_ROOT}/codepaths-schema.md. Re-read that file rather than relying on memory.
Arguments: $ARGUMENTS
CLI reference — codepaths_cli.py
The bundled CLI at ${CLAUDE_PLUGIN_ROOT}/skills/codepath-mapper/codepaths_cli.py is the canonical interface to architecture.json and codepaths.json. Don't invent verbs — every command must be one of these:
set-architecture --json -— replacearchitecture.jsonbody (stdin via quoted heredoc).add-codepath --json -— append one codepath.update-codepath --id <id> --json -— replace one codepath in place.remove-codepath --id <id>— delete one codepath.list --kind components|codepaths|categories|edges— print as JSON array.get --kind <k> --id <id>— print one item.status— counts + last-modified + render-staleness.render [--output <path>]— bake both JSONs intodocs/codepaths/architecture.html.select [--output <path>]— browser picker (used by/codepath-visualizer --select, not by this skill).
Every mutation goes through this CLI. Don't use Edit/Write/inline python3 -c '…' against architecture.json or codepaths.json — it bypasses validation and atomic writes. Don't run init or validate — neither exists; auto-init and auto-validate are built into every verb.
Exit codes: 0 success · 1 IO error · 2 argparse · 10 id not found · 11 duplicate id · 12 schema validation · 13 JSON parse · 15 cross-ref broken · 16 select aborted.
Phase 1 — Parse $ARGUMENTS
Extract the optional scope:
- Empty → full repo sweep.
- A sentence (e.g.
"invite new user flow") → codepath-name hint. - A file path → trace codepaths that touch this file (inward + outward).
- A directory path → entry points rooted in this dir.
- The flag
--remap-architecture→ rebuild architecture from scratch even if it exists. - The flag
--render-only→ skip Phases 2 and 3 entirely; jump straight to Phase 4. Use this when only the HTML template, CSS, or JSON inputs changed and no re-tracing is needed. Don't combine with a scope or--remap-architecture— those imply mapping work.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 153 lines · 121 tokens per session scan A 4a4a5bfa3860
codepath-mapper is a skill published in the GitHub repository paulbaranowski/wild-horses (12 stars, last pushed 21d ago), licensed MIT. It adds 121 tokens to every session and 1,999 once invoked, about $0.0006 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.