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 technicalpickles/pickled-claude-plugins --skill routegit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/technicalpickles/pickled-claude-plugins/route)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/route"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/route/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/technicalpickles/pickled-claude-plugins/route"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/route.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 10 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 48 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00022 | $0.00827 |
| Opus 5 | $0.00011 | $0.00413 |
| Sonnet 5 | $0.00004 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
route 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Route Stage
Analyze an enriched note against routing memory, vault rules, and generic signals. Move to destination or mark for review.
See references/pipeline.md for stage definitions and status flow.
See references/routing.md for the scoring algorithm.
See references/para.md and references/johnny-decimal.md for the two folder systems a vault may use (often both, mid-migration).
See references/routing-memory.md for the correction and learning loop.
Input
An enriched note in the inbox with status: enriched.
Process
-
Load routing context:
- Read
.routing-memory.mdfrom vault root (create with defaults if missing) - Read vault CLAUDE.md for disambiguation rules
- Run
sb vault structurefor available destinations - Run
sb note context --note "{note-path}"for keywords and signals
- Read
-
Score destinations (priority order): a. Check
.routing-memory.mdcorrections for matching topics/keywords b. Check.routing-memory.mdlearned patterns c. Apply vault CLAUDE.md disambiguation rules d. Apply generic signal scoring (perreferences/routing.md)Each destination from
sb vault structurecarries atype. For Johnny Decimal destinations (type: 'jd') also useareaandcodewhen scoring: match the note's topic to thearea, and prefer an IDcode(e.g.67.01) for a specific note or its parent categorycode(e.g.67) for a loose note. Seereferences/johnny-decimal.md. -
Apply threshold:
- Score >=
auto-route-threshold: auto-route, move file, setstatus: routed - Score < threshold: set
status: pending-review, return without moving
- Score >=
-
If auto-routing, move the file:
npx @techpickles/sb note move --from "{note-path}" --to "{destination}/"Update frontmatter:
status: routed -
If pending-review, present suggestions to human (when called by orchestrator):
- Show top 2-3 destinations with scores and reasoning
- Include "Leave in inbox" option
- If user overrides suggestion, capture correction to
.routing-memory.md
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 · 80 lines · 22 tokens per session scan A 606679ae0fc6
route is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 827 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-09-03.
Other skills, from other repositories
doc-bootstrapping
A project-documentation setup guide that creates a central set of rules, memory notes, and Diátaxis documentation folders. Diátaxis is a method that separates explanations, specifications, how-to guides, and tutorials.
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
slide-deck
When you want to draft, update, convert, or export a slide deck for a React/Next.js slide system (${SLIDEDECKREPO:-$HOME/code/your-slide-deck-site}/src/app/slides/). Writes TypeScript Slide[] arrays using your primitives (Eyebrow, Heading, Accent, Body, BulletList, Divider, TwoCol, GradientText), 12 cycling brand…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
session-cleanup
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation.…
companion-skill
An AI companion skill for developers and office workers during long-running or repetitive tasks. It provides conversation, feedback, generated lifestyle images, and messages sent through Feishu, a workplace collaboration app.