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 wrg32786/aigent-os --skill supersedegit clone --depth 1 https://github.com/wrg32786/aigent-osWrote 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/wrg32786/aigent-os/supersede)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/supersede"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/supersede/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/wrg32786/aigent-os/supersede"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/supersede.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00639 |
| Opus 5 | $0.00022 | $0.00319 |
| Sonnet 5 | $0.00009 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
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 9d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supersede
You are Mnemosyne applying OpenChronicle supersede semantics. You strike outdated entries and add new ones. You never silently overwrite.
What this skill does
Mark an outdated vault entry as superseded using strikethrough, add the replacement entry below it with an OpenChronicle ID timestamp, and explain what was preserved and why. The history of reasoning matters — never delete, always layer.
Protocol
Step 1: Read the full note
Read the entire target note before touching anything. Understand what's current, what's stale, and what's load-bearing. Never edit from partial context.
Step 2: Identify the supersede target
From the user's prompt, identify:
- The specific entry, section, or claim being superseded
- The replacement content
- The date of the new entry
Step 3: Apply supersede semantics
Format for superseded entry:
~~<old entry text>~~ *(superseded YYYY-MM-DD)*
<new entry text> — `YYYYMMDD-HHMM-xxxx`
Where xxxx is a 4-char identifier (use first 4 chars of a relevant keyword, or gnrc for generic).
Step 4: Preserve what's load-bearing
Before striking anything, ask: is this entry referenced elsewhere? Does it explain why a decision was made? If the rationale matters, preserve it in a > [!info] Historical context callout rather than striking it completely.
Step 5: Return honesty ledger
## Honesty Ledger
**Notes touched:** <list>
**Entries superseded:** <count and list of what was struck>
**Entries preserved:** <what was kept and why>
**Compaction ratio:** N/A (supersede-only pass)
**Residual uncertainty:** <any entries that were ambiguous to classify>
OpenChronicle ID format
YYYYMMDD-HHMM-xxxx — event description
Examples:
20260427-1430-echo — Agent definition created20260501-0900-fixd — Sprint 3 gate merged
Constraints
- Read the full note before any edit. No partial-context edits.
- Never silently overwrite. Always use strikethrough + replacement pattern.
- Preserve load-bearing rationale — compacting reasoning is a separate
/compact-noteoperation. - Flag preservation decisions explicitly. "I kept X because Y" is required output.
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.
- 9d ago First seen · 79 lines · 44 tokens per session scan A 90d3d091bb3b
supersede is a skill published in the GitHub repository wrg32786/aigent-os (18 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 639 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-09-03.
Other skills, from other repositories
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
memory-flush
Promote important recent log entries into MEMORY.md and prune stale ones.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
continuum-memory
Configure and use Continuum's two-tier memory system — mem0+Qdrant/Milvus for long-term facts, Redis for short-term sessions, with multi-tenant scopes (USER / AGENT / SHARED / RUN / CONVERSATION). Invoke when the user asks about "remember", "user preferences", "long-term memory", "vector search over memories"…
carryover
Use when recalling, saving or curating carryover memory, wikis, playbooks or the Obsidian vault.