progressive-disclosure

progressive-disclosure is a skill for Claude Code from datarobot-oss/datarobot-agent-skills. It costs 47 tokens per session (1,069 once invoked), scanned A, original, Apache-2.0.

A refactoring guide for splitting large DataRobot skill instructions into a shorter main file and linked reference files. Refactoring means reorganising existing material without changing what it says.

In plain words
What is it for?
Use it to reorganise oversized skill files, decide what belongs in the main instructions, create directly linked references, and preserve commands, workflows, safeguards, and examples.
Why use it?
It helps reduce context-window warnings while keeping detailed instructions available when needed. It also protects critical triggers, safety rules, and prerequisites from being moved too far away.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the datarobot-agent-skills plugin — 17 skills shipped together

Good fit Use it to reorganise oversized skill files, decide what belongs in the main instructions, create directly linked references, and preserve commands, workflows, safeguards, and examples.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/datarobot-oss/datarobot-agent-skills/progressive-disclosure
Install

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.

Any agent
npx skills add datarobot-oss/datarobot-agent-skills --skill progressive-disclosure
Clone the repo
git clone --depth 1 https://github.com/datarobot-oss/datarobot-agent-skills

Made for: Claude Code.

Or install datarobot-agent-skills, the plugin that ships this one along with the rest of its 17 skills.

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.

agentmods badge for progressive-disclosure

README.md
[![agentmods](https://agentmods.dev/badge/skills/datarobot-oss/datarobot-agent-skills/progressive-disclosure/github.svg)](https://agentmods.dev/skills/datarobot-oss/datarobot-agent-skills/progressive-disclosure)
Your own site
<a href="https://agentmods.dev/skills/datarobot-oss/datarobot-agent-skills/progressive-disclosure"><img src="https://agentmods.dev/badge/skills/datarobot-oss/datarobot-agent-skills/progressive-disclosure/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.

agentmods 80×15 button for progressive-disclosure

Your own site · 80×15
<a href="https://agentmods.dev/skills/datarobot-oss/datarobot-agent-skills/progressive-disclosure"><img src="https://agentmods.dev/badge/skills/datarobot-oss/datarobot-agent-skills/progressive-disclosure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,069 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01069
Opus 5 $0.00023 $0.00535
Sonnet 5 $0.00009 $0.00214
Haiku 4.5 $0.00005 $0.00107

Measured 11d ago against content hash 9d2a6aed5b2a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

.skills/progressive-disclosure/SKILL.md · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Progressive Disclosure

Use this repo-local meta skill to split large skills into a concise SKILL.md plus adjacent reference files. This guides content moves and reference creation; it is not a content rewrite pass.

Guardrails

  • Do not rewrite, reinterpret, simplify, or change the meaning of skill content.
  • Do not delete details because they seem verbose. Move details to reference files instead.
  • Do not change SDK guidance, commands, workflows, safety notes, or examples except to preserve links after moving content.
  • Do not edit plugin manifests, versions, CODEOWNERS, or unrelated repo metadata unless the user explicitly asks.
  • Do not create deeply nested references. Reference files should be directly linked from SKILL.md.
  • Do not move first-use trigger guidance, required safety constraints, or critical prerequisites out of SKILL.md.
  • If content needs substantive editing, stop and ask the user before making that change.

Target Shape

Keep SKILL.md focused on:

  • Frontmatter with accurate name and description
  • When to use the skill
  • Quick start or primary workflow
  • Key decision points and safety constraints
  • Direct links to reference files

Move long supporting content into files such as:

  • reference.md
  • examples.md
  • troubleshooting.md
  • platform-setup.md
  • sdk-operations.md
  • ci-cd-patterns.md

Choose names that match the moved section. Prefer a small number of meaningful files over many tiny fragments.

Use folders only when the supporting material has a clear type or grouping:

  • references/ for longer conceptual guides, examples, and workflow details
  • scripts/ for executable helpers that the skill may ask the agent to run
  • Language folders such as python/, typescript/, or r/ when a skill supports multiple programming languages

Keep these folders directly under the skill directory. SKILL.md should link directly to files inside them, such as references/workflow-details.md, without requiring the agent to follow a chain of references.

Read the full file on GitHub · 117 lines

Changes

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.

  1. 11d ago First seen · 117 lines · 47 tokens per session scan A 9d2a6aed5b2a

Subscribe to this mod's changes

progressive-disclosure is a skill published in the GitHub repository datarobot-oss/datarobot-agent-skills (25 stars, last pushed today), licensed Apache-2.0. It adds 47 tokens to every session and 1,069 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

offensive-c2-frameworks

Command and Control framework deployment, configuration, and operational tradecraft for red team engagements. Covers Cobalt Strike (malleable C2 profiles, Beacon types HTTP/HTTPS/DNS/SMB, Beacon Object Files for in-memory execution, sleep and jitter tuning, named pipe pivoting), Sliver (implant generation across…

SnailSploit/Claude-Red · 250 tokens

offensive-crypto-attacks

Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…

SnailSploit/Claude-Red · 261 tokens

offensive-parameter-pollution

HTTP parameter pollution (HPP) checklist: duplicate parameter injection, backend vs frontend parsing differences, WAF bypass via HPP, server-side vs client-side HPP, and practical exploitation patterns. Use when testing web applications for parameter handling flaws.

SnailSploit/Claude-Red · 0 tokens

offensive-wifi

Wireless / 802.11 attack methodology for red team engagements and wireless security assessments. Covers monitor-mode setup, WPA/WPA2-PSK handshake capture and PMKID attacks, WPA3 SAE downgrade and Dragonblood, WPA-Enterprise (EAP) attacks (MSCHAPv2 cracking, EAP-TLS cert theft, evil-twin RADIUS), Karma / Known Beacons…

SnailSploit/Claude-Red · 183 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

seo

Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".

addyosmani/web-quality-skills · 46 tokens