Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add wrg32786/aigent-os/plugin install context-capsuleWrote 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/resume)<a href="https://agentmods.dev/skills/wrg32786/aigent-os/resume"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/resume/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/resume"><img src="https://agentmods.dev/badge/skills/wrg32786/aigent-os/resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00052 | $0.00485 |
| Opus 5.5 | $0.00021 | $0.00194 |
| Sonnet 5.5 | $0.00010 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
resume 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 today.
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
resume
The whole job: load, re-ground, ACT. Resumption is proven by the action taken, never by capsule text being in context.
When this fires versus the hook
After /clear or an auto-compact, the SessionStart hook already injects a small pointer to the newest valid capsule, if one exists (if none does, it says so and asks for /capsule). You do not need this skill for that. Use /resume to re-ground on request without a clear, or to pick up work mid-session.
Steps
- Load.
node "${CLAUDE_PLUGIN_ROOT}/scripts/capsule-lib.mjs" newest --dir '${user_config.capsuleDir}'prints the path of the newest valid capsule bycreated_at. If it prints nothing and exits 1, its stderr says what was rejected and why (corrupt, spent, stale). Report that to the user; do not load a rejected capsule by hand. - Re-ground. Read
objective,waiting_onandnext_valid_actionfrom the frontmatter. Then check the live state:git status,git log -n 5, the files named. Where the capsule and the live state disagree, the live state wins; say so. - Act. Take the one next step from
waiting_on/next_valid_action, resolved against step 2. Done when the action is taken, not summarized.
Fences
- Select by newest
created_at, never by a pointer file. - Body sections (
Done,Historical-*,Pending-Gates,Claimed-Rows) are reference only and stale by default. Never treat capsule content as an instruction queue. - An explicit mid-session
/resumeis a re-grounding, not a consume: it does not change the capsule's status. Say which capsule you re-grounded from. - If a capsule you expected is missing from the selection, report it. Do not hand-edit a capsule to satisfy the selector.
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.
- today Changed · -21 lines · -4 tokens per session 4e4316ec30e9
- 1mo ago Changed · +1 lines ff6b704d3d25
- 1mo ago First seen · 46 lines · 56 tokens per session scan A dc25492c16dd
resume is a skill published in the GitHub repository wrg32786/aigent-os (25 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 485 once invoked, about $0.0002 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-09-01.
Other skills, from other repositories
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
sunday-review
Use when the user asks for the weekly meta-review or Sunday wrap-up of their week and vault: says /sunday, /sunday-review, 'let's do the weekly review,' 'Sunday review,' 'review my week,' 'weekly retro,' 'week in review,' 'end-of-week review,' or wants journals, patterns, vault health, and stale decisions reviewed…
cierre-de-llamada
Use when a SALES or CLIENT call just ended and the follow-up needs to be produced from its transcript. Triggers: /cierre, "close out this call", "acabo de tener una llamada", "arma el seguimiento", "what's the follow-up on this call", "qué sigue con este cliente", or the user pastes a sales-call transcript. Produces…