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 Totes-MickGOATs/opus-pocus --skill descriptio-reduciogit clone --depth 1 https://github.com/Totes-MickGOATs/opus-pocusWrote 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/totes-mickgoats/opus-pocus/descriptio-reducio)<a href="https://agentmods.dev/skills/totes-mickgoats/opus-pocus/descriptio-reducio"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/descriptio-reducio/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/totes-mickgoats/opus-pocus/descriptio-reducio"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/descriptio-reducio.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.00122 | $0.01213 |
| Opus 5 | $0.00061 | $0.00607 |
| Sonnet 5 | $0.00024 | $0.00243 |
| Haiku 4.5 | $0.00012 | $0.00121 |
Grade A, and why
descriptio-reducio 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 10d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
✨ Descriptio Reducio
"The router stops reading at 1,535 characters. Your masterpiece dies at 1,536."
Two facts about routing, both easy to forget: the router reads only the description:
frontmatter, never the body — and listings truncate. In harnesses with a listing cap
(around 1,500 characters in one measured setting; measure yours, the number is not a constant),
everything past the cliff is invisible. Authors
write descriptions front-loaded with capabilities and append the disambiguation ("NOT for: X →
other-agent") last — exactly the part that falls off.
What to scan
Every description: in .claude/skills/*/SKILL.md, .claude/agents/*.md, plugin skills and
agents, and any harness config that sets a listing cap.
Anti-patterns to find
-
Past the cliff. Description length exceeds the listing cap.
Measure the cap from inside a session, not from this file. The listing is injected into the model's system prompt and never displayed, so "render the listing" is not something a user can do — but the agent running this pass can read its own listing. Procedure:
a. Find the longest description in the repo:
for f in .claude/skills/*/SKILL.md .claude/agents/*.md; do awk '/^description:/{print length($0)-13, FILENAME}' "$f"; done | sort -rn | headb. Ask the running agent to quote that description back verbatim from its own listing, and diff it against the file. Where the quote stops is the cap. c. If nothing in the repo is long enough to truncate, the cap is unmeasurable here: this class has no instances, and the pass grades?(could not verify), notO. Do not substitute a number measured on another harness. -
NOT-for clauses last. Disambiguation after the cliff — the router sees only the capabilities, so near-miss tasks route wrong. This is the highest-impact class: a truncated NOT-for is a routing defect, not a style issue.
-
Body-only disambiguation. The routing rule lives in the agent's body ("do not use this for X") where no router ever reads it.
-
Keyword stuffing. Fifty comma-separated trigger phrases; the description becomes noise and matches everything weakly.
-
Twin descriptions. Two skills/agents whose descriptions overlap enough that routing between them is a coin flip — the distinction exists only in the bodies.
-
Description restating the body. Procedure detail in the description (steps, flags, internal paths) that costs length without aiding routing.
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.
- 10d ago First seen · 81 lines · 122 tokens per session scan A e6906997673a
descriptio-reducio is a skill published in the GitHub repository Totes-MickGOATs/opus-pocus (10 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 1,213 once invoked, about $0.0006 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
claude-md-architect
Design, create, extract, or audit CLAUDE.md files and their supporting docs/ folder structure for Claude Code projects. Use this skill whenever the user asks to create a new CLAUDE.md, extract context from a long session into a CLAUDE.md system, audit/refactor an existing CLAUDE.md that has bloated, review whether…
huggingface-llm-trainer
Train or fine-tune language models with TRL or Unsloth on Hugging Face Jobs, including SFT, DPO, GRPO, reward models, and GGUF conversion. Use for cloud LLM training; use huggingface-vision-trainer for vision tasks.
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…
memstack-product-feedback-analyzer
Use this skill when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and prioritize into actionable reports. Do NOT use for competitor analysis or market research.