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 OutlineDriven/outline-driven-development --skill cascade-dedupgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/cascade-dedup)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/cascade-dedup"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/cascade-dedup.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Agent Snooping · line 27 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- medium Rogue Agent · line 35 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00037 | $0.01702 |
| Opus 5 | $0.00018 | $0.00851 |
| Sonnet 5 | $0.00007 | $0.00340 |
| Haiku 4.5 | $0.00004 | $0.00170 |
Grade B, and why
cascade-dedup scanned grade B with 1 finding 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **Map the cascade family and zones.** The canonical baseline `system-prompt-baseline.md` is the whole-file source of truth and wins every conflict. For each output-style embed (`axiom-mode`, `builder`, `duet`, `linus` How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cascade dedup
Contract
| Field | Bound contract |
|---|---|
| Trigger | Prompt-doctrine duplication, drift, or conflict across the cascade family. |
| Authority | Human-gated: previews the target and consequence before rewriting prompt doctrine at rest, bumping the catalog releaseVersion, or editing authorized external harness embeds; every other write is reversible local, with version control as the rollback. |
| Side effect | Rewrites cascade prefixes/tails, bumps the catalog releaseVersion and re-renders package surfaces, and edits authorized external embeds. |
| Done | All canonical tails match, every strip is evidenced, divergence ledger complete, verification green. |
Inputs
- The canonical baseline file
system-prompt-baseline.md, must exist and be the agreed source of truth. - The six output-style embeds:
plugins/odin-core/output-styles/{axiom-mode,builder,duet,linus,odin,benchmark}.md. - The two external harness embeds:
~/.omp/agent/AGENTS.mdand~/.codex/AGENTS.md. - Explicit user authorization, recorded in the run, before any
benchmark.mdtail repair or authorized external embed edit.
Procedure
- Map the cascade family and zones. The canonical baseline
system-prompt-baseline.mdis the whole-file source of truth and wins every conflict. For each output-style embed (axiom-mode,builder,duet,linus,odin,benchmark), the persona prefix above the charter<role>(the second<role>in each file) is the strip zone. The tail from the charter<role>to EOF is the byte-identity invariant zone and is never a dedup target. Never touch thebenchmark.mdauto-generated margin-runner preamble. The external harness embeds~/.omp/agent/AGENTS.mdand~/.codex/AGENTS.mdare editable in place but never committable; harness-adapted tool sections are legitimate divergence. Done when: the cascade family is mapped with strip zones, invariant zones, and external embeds identified. - Verify the invariant before dedup. Copy the canonical baseline to a temporary file. For each output style, diff the canonical against the file's tail of equal byte length:
Drift in the invariant zone is a sync bug, not duplication. Repair by replacing the file's entire tail (from its charterdiff -q /tmp/canon.md <(tail -c "$(wc -c < /tmp/canon.md)" plugins/odin-core/output-styles/X.md)<role>to EOF) with the canonical content as one block; dedup edits inside the invariant zone stay forbidden. Forbenchmark.md, obtain explicit user authorization before repairing. Record each diff result. Done when: all six tails are verified byte-identical (after repair where needed), orbenchmark.mdrepair is deferred for lack of authorization. - Strip-zone scan (persona prefixes).
benchmark.mdhas no eligible strip zone (its persona prefix sits inside the auto-generated block), so scan the five hand-authored styles and skipbenchmark.md. Classify every sentence of each persona prefix asvoice,duplicate,conflict, orunique-directive:- Normalize (lowercase tokens, stopwords removed). Jaccard >= 0.65 against a baseline rule -> duplicate: strip it; the baseline copy stands.
- Jaccard >= 0.45 plus opposing modal verbs (must/never, always/must-not) -> conflict: the baseline wins; delete or rewrite the prefix line.
- Persona voice (identity, tone, register) is not a directive: keep.
- Unique directives (persona-specific rules with no baseline pair): keep. Done when: every prefix sentence is classified and every strip cites its baseline pair.
- Harness embeds. Per external file (
~/.omp/agent/AGENTS.md,~/.codex/AGENTS.md):- Internal duplication within the file, same thresholds as step 3.
- Directive-level comparison against the baseline. Classify each divergence:
harness-adaptation(names that harness's tools or commands: keep),accidental drift(same rule, mutated wording: align to baseline wording),conflict(baseline wins, unless the divergence fits harness-specific tooling). Done when: a divergence ledger with exactly one classification per divergence is produced, none unclassified.
- Apply, verify, then commit.
- Apply all repo edits: strips, conflict resolutions, tail repairs, and the
releaseVersionbump if strips or conflict resolutions occurred. Let the package-surfaces generator (scripts/render-plugin-surfaces.mjs) re-render every package surface (plugins/<id>/plugin.jsonand.claude-plugin/plugin.json) from that one literal. A run that only re-syncs an embedded baseline with zero strips is a pure sync change -> no bump. Anybenchmark.mdchange (tail repair included) ships only with explicit user authorization recorded in this run. - Run verification before committing: re-run the step 2 invariant diffs (all six tails must be byte-identical 6/6) and run
prek run --all-files. If either fails, do not commit; report the failing diff or check and the file responsible. - Only after verification passes, commit all repo files in one atomic commit (edits plus regenerated surfaces).
- External files: edit in place, never commit; end the report with an explicit warning listing every externally edited path for user review.
- Output styles load at session start: smoke-test doctrine effects in a fresh session.
Done when: the final report contains strips per file with citations, conflicts resolved with the winner named, kept harness-adaptations, externally edited paths, the
prekresult, and the invariant re-verified 6/6, with the atomic commit created only after verification passed.
- Apply all repo edits: strips, conflict resolutions, tail repairs, and the
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · -28 tokens per session b6a6fcaa2559
- 4d ago First seen · 61 lines · 65 tokens per session scan B 727119bbd413
cascade-dedup is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 2d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,702 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.
goal-prompt-drafting
Use when asked to draft copy-ready /goal objectives for long-running agents; returns one normalized one-line objective with measurable end state, grounded proof, easy-out invariants, a stop clause, and a Missing list. Not for source or remote-system changes.
handoff-prompt
Use when the user asks for a handoff, delegation, or clipboard-ready prompt for another agent: a standalone path-free prompt copied to the clipboard, confirmed by title. Not for session-snapshot briefs — use handoff; never remote, credential, publish, deploy, or irreversible.
publish-branch
Use when asked to publish the checked-out branch: commit and push it on whatever branch it is, the default branch included. Not for creating branches, PRs, force pushes, or pushing any other branch; when the request excludes the default branch, use commit-push-current.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.