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 agentmods add skills/technicalpickles/pickled-claude-plugins/distill-rulesnpx skills add technicalpickles/pickled-claude-plugins --skill distill-rulesgit 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/distill-rules)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/distill-rules"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/distill-rules.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00529 |
| Opus 5 | $0.00010 | $0.00264 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
distill-rules 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 4d 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.
What it actually says
Distill Rules
Review accumulated routing corrections in .routing-memory.md and propose updates to the vault's CLAUDE.md routing rules.
See references/routing-memory.md for correction format and learning loop.
Process
-
Read
.routing-memory.mdfrom vault root -
Read vault CLAUDE.md
-
Analyze corrections for patterns:
- Group corrections by destination
- Identify repeated corrections (same type of note going to same destination)
- Look for corrections that contradict existing CLAUDE.md rules
-
Propose updates:
- New edge case mappings for disambiguation sections
- New category table entries
- New learned patterns for
.routing-memory.md - Corrections to existing rules that have been consistently overridden
-
Present proposals to user:
Found {n} patterns in {m} corrections: 1. Add edge case: "{scenario}" -> {destination} Based on: {n} corrections over {date range} 2. Add to category table: "{tool}" under {area} Based on: {n} corrections 3. Update rule: "{old rule}" -> "{new rule}" Based on: consistently overridden {n} times Apply these updates? (A) Apply all (B) Review individually (C) Skip for now -
Apply selected updates:
- Edit vault CLAUDE.md with new rules
- Move applied corrections to an
## Archivedsection in.routing-memory.md - Promote stable patterns to
## Patterns Learned
Constraints
- Never auto-apply. Always present proposals for approval.
- Preserve existing CLAUDE.md structure and formatting
- Archive corrections, don't delete them (audit trail)
- Only propose rules backed by multiple corrections (minimum 2)
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.
- 4d ago First seen · 66 lines · 20 tokens per session scan A 3a5e0e26e998
distill-rules is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (10 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 529 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-08-31.
Other skills, from other repositories
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
n8n:create-pr
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
n8n:reproduce-bug
Reproduce a bug from a Linear ticket with a failing test. Expects the full ticket context (title, description, comments) to be provided as input.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.