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 CrumbtrailDev/crumbtrail-cli --skill new-path-paritygit clone --depth 1 https://github.com/CrumbtrailDev/crumbtrail-cliWrote 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/crumbtraildev/crumbtrail-cli/new-path-parity)<a href="https://agentmods.dev/skills/crumbtraildev/crumbtrail-cli/new-path-parity"><img src="https://agentmods.dev/badge/skills/crumbtraildev/crumbtrail-cli/new-path-parity/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/crumbtraildev/crumbtrail-cli/new-path-parity"><img src="https://agentmods.dev/badge/skills/crumbtraildev/crumbtrail-cli/new-path-parity.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.00099 | $0.01991 |
| Opus 5.5 | $0.00040 | $0.00796 |
| Sonnet 5.5 | $0.00020 | $0.00398 |
| Haiku 4.5 | $0.00010 | $0.00199 |
Grade A, and why
new-path-parity 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The new path parity gap
A surface gets reimplemented: a second renderer, a new route, a rewritten editor, a v2 engine behind the same button. The new implementation covers the common cases and quietly drops behaviours the old one had. Parity patches then arrive one property at a time, and the class refills every time a feature lands on the old path only.
The triage question for this archetype is unusual. Before you ask what the bug is, ask which path served the failing action. Everything below is about answering that from a recording.
Symptom
The reporter says the feature works one way and not another: on the old screen but not the new one, on the previous release but not this one, in the classic view but not the rebuilt view. The steps are the same. The data is the same. Only the surface changed.
A second common phrasing: a property the reporter relies on is simply not there any more. No error, no failure, just an option that stopped being honoured.
What Crumbtrail can see
Crumbtrail has no concept of a code path. It records one browsing session at a time and cannot tell you which module, component tree or engine version handled a request. Nothing in a recording says v1 or v2. If a skill told you otherwise it would be wrong.
What a recording does carry, and what makes the comparison possible:
- Navigation events with the exact URL and the transition that produced it, so two runs can be aligned by route.
- Every request and response with method, URL, status, duration and body. Bodies are summarized when large and fields are replaced with a redaction marker when the policy considers them sensitive, so you can rely on the presence and shape of a field more than on its value.
- An environment snapshot taken in the browser: user agent, browser name and version, operating system, viewport, locale and time zone.
- Backend request start, end and error records, but only where the backend SDK is installed.
- Database row changes with the table, the primary key, the before and after column values and a call site file and line, but only where the database adapter is installed.
listSessionsacceptsreleaseandbuildfilters, which is the one place a recording carries a version label at all, and only when the app supplied one.
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 Changed 5d6d04b630c6
- 1mo ago First seen · 175 lines · 99 tokens per session scan A ca59bcd51997
new-path-parity is a skill published in the GitHub repository CrumbtrailDev/crumbtrail-cli (0 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 1,991 once invoked, about $0.0004 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 skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.