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/dustinvk/wherefore/supersedenpx skills add DustinVK/wherefore --skill supersedegit clone --depth 1 https://github.com/DustinVK/whereforeWrote 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/dustinvk/wherefore/supersede)<a href="https://agentmods.dev/skills/dustinvk/wherefore/supersede"><img src="https://agentmods.dev/badge/skills/dustinvk/wherefore/supersede.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.00095 | $0.01296 |
| Opus 5 | $0.00048 | $0.00648 |
| Sonnet 5 | $0.00019 | $0.00259 |
| Haiku 4.5 | $0.00010 | $0.00130 |
Grade A, and why
supersede 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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wherefore: supersede
Retire an existing wherefore entry by marking it superseded (with a pointer to its
replacement) or obsolete (context gone, no replacement). Updates the entry
file and adds a visible banner, so neither the ask skill nor a human skimming
raw files is left guessing. The entry's frontmatter is the single source of
truth.
This skill is the only writer of decision status. Plan items have their own status
machine (todo/doing/done/dropped) that never touches a decision's status; if
work in the slate skill needs to retire or replace a decision, it routes here, not
through slate.
No em dashes. Periods, commas, colons, semicolons, or parentheses instead. Firm project rule.
Never delete anything under a wherefore/ data dir. Retire, do not delete.
Workflow
-
Find the target entry. Locate
wherefore/log/<slug>.mddirectly. If you only have a date or partial name, dump the entry frontmatter to find the slug:for f in wherefore/log/*.md; do awk -v F="$f" 'BEGIN{print "=== " F " ==="} /^---[[:space:]]*$/ { n++; if (n==2) exit; next } n==1 { print }' "$f" doneIf not found, say so clearly. If already
supersededorobsolete, show the current state and ask the user before overwriting; don't silently re-supersede. -
Determine the operation.
- Superseded by: the user names a replacement slug (an existing entry) or a replacement description (a discussion not yet logged). If the replacement isn't logged yet, note it and proceed; the link will be a placeholder.
- Obsolete: no replacement. The decision was abandoned or its context no longer exists.
-
Edit the target entry's frontmatter:
Superseded:
status: superseded superseded_by: <new-slug> superseded_date: YYYY-MM-DDObsolete:
status: obsolete superseded_date: YYYY-MM-DD -
Add a one-line banner as the first body line of the target entry, after the closing
---of the frontmatter, before## Summary. No emoji.
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.
- 5d ago First seen · 114 lines · 95 tokens per session scan A 974be8bee1b0
supersede is a skill published in the GitHub repository DustinVK/wherefore (1 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 1,296 once invoked, about $0.0005 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
bootstrap
Scaffold or retrofit documentation-led conventions (AGENTS.md, CLAUDE.md, CONVENTIONS.md, ADR catalogue, plan/ queue, agent/ coordination) into a repo. Use when the user asks to "set up conventions", "bootstrap ADRs", "scaffold the documentation-led layout", "add AGENTS.md and a plan queue", or invokes /bootstrap.…
decision-backfill
Use when auditing an existing codebase, documentation set, plans, RFCs, or git history for architecture decisions that were made but never recorded as ADRs, and when triaging potential records before drafting them.
decision-memory
Use when planning, designing, reviewing, or changing code in a repository that keeps ADRs (usually docs/adr) — to load the decisions that already govern the work, check a plan or diff against them, or record a new decision. Also use when a choice feels already-settled and you cannot find where it was settled.
actual
Feature-complete companion for the actual CLI, an ADR-powered CLAUDE.md/AGENTS.md generator. Runs and troubleshoots actual adr-bot, status, auth, config, runners, and models, plus the Actual AI platform surface: login, logout, whoami, and advisor (org-scoped architecture Q&A). Covers all 5 runners (claude-cli…
audit
Audit a documentation-led repo against its own conventions — contiguous ADR numbering, INDEX sync, plan/ coverage, required sections, status validity, cross-reference resolution, language mandate, ADR-privacy leaks into user-visible code, cross-worktree collisions (duplicate numbers, duplicate plan ownership, same ADR…
agent-wave
Orchestrate a wave of parallel agents over the plan/todo queue in a documentation-led repo — asks how many agents, the budget (items/waves, with hours as a soft cap), and whether to checkpoint after each wave or run continuously. Spawns isolated worktree subagents, assigns one queue item each, collects results. Use…