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 ayeshakhalid192007-dev/graph-engineering-crash-course --skill supersede-claimgit clone --depth 1 https://github.com/ayeshakhalid192007-dev/graph-engineering-crash-courseWrote 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/ayeshakhalid192007-dev/graph-engineering-crash-course/supersede-claim)<a href="https://agentmods.dev/skills/ayeshakhalid192007-dev/graph-engineering-crash-course/supersede-claim"><img src="https://agentmods.dev/badge/skills/ayeshakhalid192007-dev/graph-engineering-crash-course/supersede-claim/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/ayeshakhalid192007-dev/graph-engineering-crash-course/supersede-claim"><img src="https://agentmods.dev/badge/skills/ayeshakhalid192007-dev/graph-engineering-crash-course/supersede-claim.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.00043 | $0.00940 |
| Opus 5 | $0.00022 | $0.00470 |
| Sonnet 5 | $0.00009 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
supersede-claim 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 10d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
supersede-claim
Reads an existing claim and a piece of new evidence, decides whether the
new evidence actually corrects that claim, and if so adds a new node for
the correction plus a supersedes edge — leaving the old node in place,
flagged stale, never overwritten.
Instructions
You are a Claude Code skill implementing the supersession-chain
pattern. Follow these steps in order:
- Read every existing claim first, noting its id, its stated value, its source, and its current status. Hold the full set in mind — you need to check the new evidence against all of them, not just the one you expect it to correct.
- Read the new evidence. Default to the claims and evidence in this
kit's
README.mdunless the user gives you different ones. - For each existing claim, decide whether the new evidence directly corrects it. "Directly corrects" means the new evidence states a different value for the same fact the claim asserts, or explicitly says the old value was wrong. Evidence that comes from the same source document but addresses a different fact does not correct anything — check each claim on its own terms, not by association with whatever else in the document changed.
- For every claim the new evidence does not correct, leave it untouched. Do not change its status, its value, or anything else about it. Say explicitly in your report that you checked it and found no correction, so a reader can tell "checked and unaffected" apart from "never looked at."
- For every claim the new evidence does correct, create a new node holding the corrected value and its own source (the new evidence), with a fresh id distinct from the old claim's id.
- Add one
supersedesedge per correction, from the new node to the old node it corrects. The direction matters: the new node supersedes the old one, never the reverse. - Update the old node's status to
stale. Do not delete it, do not overwrite its value or source fields — the only thing that changes on the old node is its status. - Report the result: for every existing claim, either "unchanged" (with a one-line reason) or "superseded" (with the new node's id, the edge, and the old node's new status). Never report a claim without one of these two outcomes.
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.
- 10d ago First seen · 87 lines · 43 tokens per session scan A 9dd6ecfe42f7
supersede-claim is a skill published in the GitHub repository ayeshakhalid192007-dev/graph-engineering-crash-course (5 stars, last pushed 15d ago), licensed MIT. It adds 43 tokens to every session and 940 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-31.
Other skills, from other repositories
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
open-weights
Use when choosing an open-weight LLM and clearing it for use — which family and size fit the task, the hardware and the budget, and above all whether the license permits shipping. Owns the license-class map (OSI-open versus custom-community versus non-commercial), the always-verify-the-model-card rule, size-to-VRAM…
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
prompt-engineering
Use when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is building-agents), NOT a standing CI eval…
ollama
Use when running open-weight LLMs locally with Ollama — pulling and tagging models, calling the local API, picking a quantization or GGUF, writing Modelfiles, and sizing VRAM and RAM for the machine at hand. NOT remote or managed GPU serving and autoscaling (that is runpod), NOT downloading raw weights or datasets…
ring:adopting-lib-commons-huma-wrapper
Adopting the lib-commons/v5 shared Huma (OAS 3.1) OpenAPI wrapper + RFC 9457 problem model (commons/net/http/{openapi,problem}) in a Lerian Go service: wire openapi.New/ServeSpec + problem.Install (central >=500 scrub) on BOTH runtime and spec-gen paths, the per-rail problem.MapError flex seam, and rename-only spec…