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 tomzx/agents --skill supersede-decisiongit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/supersede-decision)<a href="https://agentmods.dev/skills/tomzx/agents/supersede-decision"><img src="https://agentmods.dev/badge/skills/tomzx/agents/supersede-decision/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/tomzx/agents/supersede-decision"><img src="https://agentmods.dev/badge/skills/tomzx/agents/supersede-decision.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.00028 | $0.01138 |
| Opus 5 | $0.00014 | $0.00569 |
| Sonnet 5 | $0.00006 | $0.00228 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
supersede-decision 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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supersede Decision
Records that one decision replaces another.
Updates the old decision to Superseded by [N], annotates the new decision with the reverse link, and validates that the relationship is sound (no cycles, no re-superseding an already-terminal decision).
Use this instead of editing decision files by hand when a replacement ADR is adopted.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - Two existing decisions under
.sdlc/knowledge/decisions/: the one being replaced (old-decision) and its replacement (new-decision).
Arguments
| Position | Name | Required | Description |
|---|---|---|---|
| 1 | old-decision |
yes | The decision being replaced. |
| 2 | new-decision |
yes | The decision that replaces it. |
Both arguments accept a bare number (e.g. 7) or a filename/path (e.g. 7-use-redis.md); leading zeros are tolerated when matching (0007 resolves the same as 7).
A number resolves to the file N-<slug>.md in the decisions directory.
Steps
- Resolve both arguments to files under
.sdlc/knowledge/decisions/(or the project's existing ADR directory, same resolution ascreate-decision), applying theSDLC_DIRread fallback inshared.mdwhen the repo path is absent. - Validate the relationship against the Rules below. Stop and report on any violation; change no files.
- In the old decision, set frontmatter
status: Superseded by [N]and update the body**Status:**line to match. The frontmatter remains the source of truth; the body line is kept in sync for readers. - In the new decision, add frontmatter
supersedes: N(only if absent) and a**Supersedes:** N-<slug>line directly beneath**Status:**. - Report the result and emit the outcome.
Rules
- Refuse if
old-decisionis alreadyDeprecatedorSuperseded by [...]. Terminal states cannot be re-superseded; point the caller at the live decision at the head of the chain instead. - Refuse if
new-decisionisDeprecatedorSuperseded by [...]. A retired decision cannot replace a live one. - Refuse if the two resolve to the same file.
- Refuse a cycle: follow the
supersedeslinks fromnew-decisionand refuse if any reachesold-decision(i.e. the replacement already transitively supersedes the target). - Edit only status fields. Supersession is a lifecycle transition, not a content revision; do not rewrite context, options, or consequences.
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.
- 7d ago First seen · 98 lines · 28 tokens per session scan A 16ba021a5175
supersede-decision is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,138 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.