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 cpliakas/claude-code-engineering-leaders --skill audit-routing-qualitygit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/audit-routing-quality)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/audit-routing-quality"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/audit-routing-quality/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/cpliakas/claude-code-engineering-leaders/audit-routing-quality"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/audit-routing-quality.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.00075 | $0.02230 |
| Opus 5 | $0.00037 | $0.01115 |
| Sonnet 5 | $0.00015 | $0.00446 |
| Haiku 4.5 | $0.00007 | $0.00223 |
Grade A, and why
audit-routing-quality 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Routing Quality
Read the Tech Lead's ## Routing Outcomes history and produce a report
recommending narrowing actions for specialists that are consistently over-routed.
Advisory only: this skill never modifies ## Registered Specialists,
## Project Code Area Overrides, or any specialist agent file.
How This Complements /audit-routing-table
| Skill | Input | Purpose | When to run |
|---|---|---|---|
/audit-routing-table |
Memory file structure and agent files | Structural hygiene (orphan overrides, broken pointers, redundant overrides, thin descriptions) | After onboarding, after adding specialists, when routing seems broken |
/audit-routing-quality |
## Routing Outcomes history |
Outcome-based narrowing (specialists consulted frequently but adding no value) | After accumulating outcome history, when routing feels noisy |
The two skills complement each other. Run /audit-routing-table to fix
structural problems; run /audit-routing-quality to tighten trigger fit based
on data.
Process
Step 1: Read the Memory File
Read .claude/agent-memory/engineering-leaders-tech-lead/MEMORY.md.
Missing memory file:
No Tech Lead memory file found. Run /onboard or /add-specialist to create one.
Exit without error.
Missing or empty ## Routing Outcomes section:
No routing outcome history recorded yet. Run /plan-implementation on a story
that routes to specialists, then return to /audit-routing-quality once outcome
rows have been appended.
Exit without error.
Step 2: Parse the ## Routing Outcomes Table
Extract every data row from the ## Routing Outcomes table. Ignore the header
row and the separator row. For each data row, parse the five columns:
Date, Story Slug, Specialist, Value, Note.
Skip ROLLUP rows (where Story Slug is ROLLUP) for the purpose of
aggregation. They summarize already-compressed history and their counts are
not double-counted.
Step 3: Aggregate Per Specialist
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 · 241 lines · 75 tokens per session scan A 9c5b508a2291
audit-routing-quality is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 18d ago), licensed MIT. It adds 75 tokens to every session and 2,230 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…