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 Totes-MickGOATs/opus-pocus --skill obliviate-fossiliumgit clone --depth 1 https://github.com/Totes-MickGOATs/opus-pocusWrote 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/totes-mickgoats/opus-pocus/obliviate-fossilium)<a href="https://agentmods.dev/skills/totes-mickgoats/opus-pocus/obliviate-fossilium"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/obliviate-fossilium/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/totes-mickgoats/opus-pocus/obliviate-fossilium"><img src="https://agentmods.dev/badge/skills/totes-mickgoats/opus-pocus/obliviate-fossilium.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.00163 | $0.01108 |
| Opus 5 | $0.00081 | $0.00554 |
| Sonnet 5 | $0.00033 | $0.00222 |
| Haiku 4.5 | $0.00016 | $0.00111 |
Grade A, and why
obliviate-fossilium 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 12d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
✨ Obliviate Fossilium
"Your memory file remembers things that stopped being true in July."
Memory files accrete like sediment: every correction keeps the old wording as a warning, every migration leaves "note: this changed" markers, every count gets hand-typed and never updated. The model reads all of it, every session, and weighs the fossil as heavily as the living rule.
What to scan
The root memory file, every nested one, whatever the repo names them (CLAUDE.md, AGENTS.md),
user-global memory files with the user's consent, and any doc the instruction layer tells agents
to read routinely.
Anti-patterns to find
- Migration-relative phrasing. "This used to say X until ", "note this changed", "the old rule was…". Useful for the week after the change; a fossil forever after. The current fact is the only fact the model needs.
- Retraction narratives in the hot path. Paragraph-length stories of how a claim was wrong and got corrected. The correction earns its context; the story doesn't.
- Typed facts that drift. Hand-written counts, sizes, version numbers, dates ("the suite has 5,738 tests") that go stale silently. Symptom: two different numbers for the same fact in one file.
- History as instruction. Vendor-adoption sagas, decision back-stories, who-ruled-what timelines living inline where a decision-record pointer would do.
- Restated rules. The same rule paraphrased in three sections because each author feared the reader would miss it (also feeds Contradicto Revelio when the copies drift apart).
- Panic-marker sediment. ⚠ markers on resolved history (→ Quietus Capslockius grades the volume; this pass relocates the content).
- Sheer size. Official guidance targets lean memory files (on the order of a couple hundred lines); multi-thousand-line roots are paying context tax every single session.
Fix prescriptions
| Finding class | Fix |
|---|---|
| Migration-relative phrasing | State only the current fact; keep the pointer to the decision record if one exists |
| Retraction narratives | Move the narrative VERBATIM to an archive file (docs/history.md or the repo's knowledge dir); the hot path keeps one sentence |
| Typed facts | Replace with the derivation: the command that computes the fact (ls … | wc -l), stated as "derive it, don't quote it" |
| History as instruction | One-line pointer to the ADR/knowledge file; the saga lives there |
| Restated rules | Single-source: the rule once, in its home section; pointers elsewhere |
| Marker sediment | Markers only on live hazards; archive the rest with the narratives |
| Size | After the above, re-measure. If still oversized, hand candidates to Accio Rulebook (path-scoped extraction) and Avada Verbosa (ablation) |
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.
- 12d ago First seen · 72 lines · 163 tokens per session scan A 213c8f4c01b3
obliviate-fossilium is a skill published in the GitHub repository Totes-MickGOATs/opus-pocus (10 stars, last pushed 1mo ago), licensed MIT. It adds 163 tokens to every session and 1,108 once invoked, about $0.0008 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
strategic-compact
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction. Use when a session is approaching a context limit and a task phase is a natural place to compact.
unified-memory
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
agents-md-improver
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or…
agents-md-revise
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end…
report
Writes the session final report to a file, then prints only the path and a one-line summary. Fires when the prompt contains "Report per memstack:report", and also when the prompt begins with a standing trigger configured through MEMSTACKREPORTONTASKPROMPTS or MEMSTACKREPORTTRIGGERS. Dormant otherwise.
token-optimization
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'token stack', or 'TokenStack', or asks about extending context window capacity. Covers TokenStack, the built-in compression proxy that shrinks Claude Code tool output before it reaches the Anthropic API. Do NOT use for…