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 ToruAI/toru-claude-agents --skill megg-stategit clone --depth 1 https://github.com/ToruAI/toru-claude-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/toruai/toru-claude-agents/megg-state)<a href="https://agentmods.dev/skills/toruai/toru-claude-agents/megg-state"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/megg-state/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/toruai/toru-claude-agents/megg-state"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/megg-state.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.00023 | $0.00332 |
| Opus 5.5 | $0.00009 | $0.00133 |
| Sonnet 5.5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
megg-state 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- megg-state — 89% identical, 2 lines differ
What it actually says
Session State Management
Capture or manage session state for cross-session handoff.
Process
Default (no argument) - Capture State
- Review what was worked on in this session
- Summarize into this format:
## Working On
[One-liner: the main task/goal]
## Progress
- [What's been done]
- [Current status]
## Next
- [Immediate next steps]
## Context
[Relevant files, blockers, pending decisions - keep brief]
-
Call the
mcp__megg__statetool with the content:mcp__megg__state({ content: "<formatted content>" }) -
Confirm to user that state was saved
clear - Clear State
- Call
mcp__megg__state({ status: "done" }) - Confirm state was cleared
show - Display Current State
- Call
mcp__megg__state()with no arguments - Display the current state or "No active state"
Notes
- State is ephemeral - overwritten each session
- Auto-expires after 48 hours or when marked done
- Hard limit of 2k tokens to prevent bloat
- Keep content concise and actionable
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.
- 1mo ago First seen · 60 lines · 23 tokens per session scan A 2dd32e7eea6b
megg-state is a skill published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 332 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
principle-guard-the-context-window
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
session-handoff
Create consistent session handoff documents for context transfer between sessions. Use when closing a session, reaching 75% token consumption, or when user requests handoff. Ensures proper YAML headers for metrics collection, LF line endings, and complete documentation of progress, decisions, and next steps.
domain-extract
Extract domain knowledge from existing project sources and generate domain rules. Also handles vault sync and domain listing.
capture-practice
Captures an insight or practice discovered during work and registers it in the dotforge practices/inbox.
update
Integrate external info (research, status changes, reference material, deliverables) into the ops repo's knowledge base. Drop files in .update/ or pass content inline.
harden-memories
Audit the bd remember store and recommend which entries to prune, so each one earns its per-session bd prime injection cost. Read-only: it proposes a triage table plus the exact bd forget / migration commands; you run them. Use when bd remember entries have accumulated, feel stale, redundant, or conflicting, or when…