Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/apurvbazari/claude-plugins/progressive-disclosure)<a href="https://agentmods.dev/skills/apurvbazari/claude-plugins/progressive-disclosure"><img src="https://agentmods.dev/badge/skills/apurvbazari/claude-plugins/progressive-disclosure.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.1 | $0.00073 | $0.01512 |
| Opus 5 | $0.00036 | $0.00756 |
| Sonnet 5 | $0.00015 | $0.00302 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
progressive-disclosure 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 6d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progressive Disclosure — SKILL.md Slimming
Apply a reusable rubric for deciding what stays inline in a SKILL.md versus what gets pushed into references/ (inert content) or scripts/ (long bash). Goal: smaller always-loaded context per skill invocation, without losing fidelity.
Guard
Target file path MUST match **/skills/<name>/SKILL.md. If the target is a CLAUDE.md, README.md, agent file, or hook script, abort with:
Progressive-disclosure rubric is calibrated for SKILL.md only. Target
<path>is not a SKILL.md; aborting.
The other file types have different audiences and different criteria.
Step 1: Measure the file
Run:
TARGET="<path-to-SKILL.md>"
total_lines=$(wc -l < "$TARGET")
heading_count=$(grep -c '^##\? ' "$TARGET")
long_blocks=$(awk '/^```/{n++; if(n%2){start=NR}else{if(NR-start>20)print " block ending line "NR" ("NR-start" lines)"}}' "$TARGET")
echo "File: $TARGET"
echo "Total lines: $total_lines"
echo "Headings: $heading_count"
echo "Code blocks > 20 lines:"
echo "$long_blocks"
If total_lines <= 100, tell the user the file is already under the soft threshold and ask whether to proceed anyway. Below the threshold, the rubric usually finds nothing worth extracting.
Step 2: Identify extraction candidates
Walk every ## Step section of the SKILL.md and apply the rubric:
| Pattern in SKILL.md | Threshold | Destination | Stub form |
|---|---|---|---|
| Verbatim prompt template (question text + option labels + per-option behavior) | > 10 lines | references/prompts/<topic>.md |
Use the prompt template at \references/prompts/.md` — verbatim, do not paraphrase.` |
| JSON / YAML schema example | > 15 lines | references/schemas/<name>.md |
See schema at \references/schemas/.md`. Match output to this schema.` |
| Decision tables | > 10 rows | references/tables/<topic>.md |
Lookup table at \references/tables/.md` — apply per the headers there.` |
| Long enumeration of options or rules | > 10 items with multi-line explanations | references/<topic>.md |
Apply the rules documented in \references/.md`.` |
| Bash block | > 20 lines | scripts/<name>.sh (NOT references/) |
bash "${CLAUDE_PLUGIN_ROOT}/scripts/<name>.sh" <args> |
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.
- 6d ago First seen · 101 lines · 73 tokens per session scan A a830a5785504
progressive-disclosure is a skill published in the GitHub repository ApurvBazari/claude-plugins (0 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,512 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
repo-harness
Route explicit repo-harness setup, planning, execution, verification, and handoff actions through deterministic repository state.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-orient
Retrieve relevant functions, callers, spec sections, and insertion points from OpenLore before reading source files. Use when starting work that needs structural orientation in an existing codebase.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.