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 dryvist/claude-code-plugins --skill resumegit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/resume)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/resume"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/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/dryvist/claude-code-plugins/resume"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/resume.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.00056 | $0.01212 |
| Opus 5.5 | $0.00022 | $0.00485 |
| Sonnet 5.5 | $0.00011 | $0.00242 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade B, and why
resume scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
if not, find the most recent under `<HOME>/.claude/plans/`. How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume
Continue unfinished work in a session that has no memory of how it got here. The core rule: trust live state, never prose. A resume prompt, a plan file, or a prior summary describes what was true. Before acting, verify what is true.
This exists because resuming cold is common and easy to get wrong: the failure mode is redoing work that already shipped, or acting on a claim that has since gone stale.
State warning: everything below drifts. A PR called "open" in the prompt may be merged; a plan item marked
[ ]may be done. Re-derive all of it now.
Step 1: Locate the work
- Read the plan file. The resume prompt should name it (
<HOME>/.claude/plans/<slug>.md); if not, find the most recent under<HOME>/.claude/plans/. TaskList— the pending/in-progress items.- The directory the work lives in — the prompt's
cdblock. Only if that is missing andgit rev-parse --is-inside-work-treesucceeds, widen the search withgit worktree list.
Step 2: Re-derive live state (never trust the prompt's claims)
For every claim the prompt or plan makes, run the check that confirms it. Pick the cheapest evidence source that can actually falsify the claim:
| Evidence source | Confirms |
|---|---|
| The file itself | "file Y still needs Z" — read it; the change may already be there |
| Test or build output | "it works" / "it's broken" — run it |
TaskList and the plan checkbox |
a claim, never proof — treat as the thing to verify, not the verification |
| Filesystem | "the artifact was generated", "the config exists" |
| Version control (repository only) | "branch X is pushed", "PR #N is open", "already merged" |
The version-control row is gated:
git rev-parse --is-inside-work-tree >/dev/null 2>&1
When it succeeds, add gh pr view <N> --json state,mergedAt (a PR called open
may be merged), git status -sb, and gh pr list --state merged to catch work
already shipped.
To find commits not yet on the default branch, run this as one block — the resolution and its use must share a shell (see ARCHITECTURE.md):
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 Changed · +1 lines ad1754a3d577
- 24d ago Changed · -42 tokens per session 21e84ecc83c3
- 1mo ago First seen · 110 lines · 98 tokens per session scan B 294a29ed6aca
resume is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,212 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…