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/ani-hq/session-warden/claude-codenpx skills add Ani-HQ/session-warden --skill claude-codegit clone --depth 1 https://github.com/Ani-HQ/session-wardenWrote 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/ani-hq/session-warden/claude-code)<a href="https://agentmods.dev/skills/ani-hq/session-warden/claude-code"><img src="https://agentmods.dev/badge/skills/ani-hq/session-warden/claude-code.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.1 | $0.00036 | $0.00198 |
| Opus 5 | $0.00018 | $0.00099 |
| Sonnet 5 | $0.00007 | $0.00040 |
| Haiku 4.5 | $0.00004 | $0.00020 |
Grade A, and why
session-warden-route 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 yesterday.
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.
What it actually says
session-warden route (Claude Code)
Extra Anthropic quota is gone. You are the frontier harness. Do not spend yourself on busywork.
Before you work
session-warden route --task "$THE_ASK" --host claude-code --json
Read worker, reason, costClass, self.
- If
selfis true, do the work yourself. - Otherwise:
session-warden run --worker "$WORKER" --prompt "$THE_ASK"
Use that result. Do not re-do it with Opus "just to check" unless the user asked.
Frontier still wins for architecture, multi-file refactors, and security. Rate-limited providers are skipped automatically.
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.
- yesterday First seen · 28 lines · 36 tokens per session scan A 7e7524b9b002
session-warden-route is a skill published in the GitHub repository Ani-HQ/session-warden (5 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 198 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-04.
Other skills, from other repositories
memory-config
Diagnose and configure MemSearch memory behavior. Use when the user asks about MemSearch configuration, plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions.
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
openclaw-plugin
This plugin is a thin adapter between OpenClaw and LycheeMem. It does not replace memory-core, does not claim plugins.slots.memory, and does not duplicate LycheeMem algorithms.
lycheemem
Forceful operating rules for using LycheeMem as the primary structured long-term memory path inside OpenClaw.
memory
Use LycheeMem as Claude Code's structured long-term memory for prior conversations, user preferences, project decisions, timelines, and durable facts.