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-tablegit 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-table)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/audit-routing-table"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/audit-routing-table/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-table"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/audit-routing-table.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.01341 |
| Opus 5 | $0.00030 | $0.00671 |
| Sonnet 5 | $0.00012 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
audit-routing-table 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Routing Table
Audit the Tech Lead's specialist routing model in
.claude/agent-memory/engineering-leaders-tech-lead/MEMORY.md for four
categories of hygiene issues. Produces a report with recommended actions.
Does not modify any files.
Process
1. Read the Memory File
Read .claude/agent-memory/engineering-leaders-tech-lead/MEMORY.md.
If the file does not exist or is empty, report:
No Tech Lead memory file found. Run /onboard or /add-specialist to create one.
And exit.
Parse two sections:
- Registered Specialists — extract the list of
<agent-name>and optional<path>from each bullet. Default path isagents/<agent-name>.mdwhen no path is given. - Project Code Area Overrides — extract each
| signal | agent-name |row from the table, ignoring the header and separator rows.
2. Run Four Checks
For each check, collect findings into a list. A finding includes:
- The specific entry that triggered it
- A one-line explanation of why it is a problem
- A recommended action
Check 1: Orphan Overrides
For each row in ## Project Code Area Overrides, verify the target agent name
appears in ## Registered Specialists.
Finding: override row targets <agent-name> which is not in ## Registered Specialists.
Recommended action: Either register the agent with /add-specialist <agent-name> or remove the orphan override row.
Check 2: Broken Pointers
For each entry in ## Registered Specialists, attempt to read the agent file
at the specified path (or agents/<agent-name>.md).
Use Glob to check whether the file exists. If the file is not found:
Finding: registered specialist <agent-name> points to <path> which does
not exist.
Recommended action: Correct the path in ## Registered Specialists, or
remove the entry if the specialist is no longer used. If the agent is from an
external plugin that is not installed locally, this may be expected — verify
with the plugin author.
Check 3: Redundant Overrides
What ships with it
1 file 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 · 195 lines · 60 tokens per session scan A 999d5a17d8c9
audit-routing-table is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 1,341 once invoked, about $0.0003 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…