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 rfxlamia/pocketto --skill pocket-closinggit clone --depth 1 https://github.com/rfxlamia/pockettoWrote 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/rfxlamia/pocketto/pocket-closing)<a href="https://agentmods.dev/skills/rfxlamia/pocketto/pocket-closing"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/pocket-closing/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/rfxlamia/pocketto/pocket-closing"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/pocket-closing.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.00071 | $0.05310 |
| Opus 5.5 | $0.00028 | $0.02124 |
| Sonnet 5.5 | $0.00014 | $0.01062 |
| Haiku 4.5 | $0.00007 | $0.00531 |
Grade A, and why
pocket-closing 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 13d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pocket Closing
The closing stage of the Pocket pipeline. Use it when the user asks to close a reviewed phase or plan; an explicit end-to-end request that includes closeout also authorizes this stage. Reconcile verdicts against the execution log, advance only a passing phase, and append a readable record of that phase. A passing verdict alone is not authorization to close.
Core principle: Current verdicts decide. pocket-closing never re-reviews or overrides them; it reconciles the task verdict artifacts with log.json, advances only a passing phase, and records what the sources support. No current clean verdict, no phase advance.
Core v4 lifecycle boundary
pocket-closing is a Core workflow. Core keeps plan closure local-first: log update and log close commit lifecycle state and neutral events with CLI CONTRACT=3 and lifecycle schema 1 for unpatched documents or 2 for stacked plans. Core does not call gh, does not merge pull requests, and does not close issues. An optional, compatible Enterprise adapter may later reconcile the plan-closed event. Closing locally succeeds without Enterprise, and pending events remain available for replay.
If a projection write needs recovery, run pocketto-pi lifecycle repair <spec_dir> --json --contract 3 before pocketto-pi lifecycle drain <spec_dir> --json --contract 3. Repair preserves task progress and fails closed when task state is unrecoverable; drain replays pending events in order without creating events. Active v3 plans with progress stay on v3 and are never silently converted.
Position in Pocket Bundle
pocket-grinding → pocket-planning → pocket-structuring → pocket-development → POCKET-CLOSING
↑
After the user authorizes closeout
and pocket-development's phase-level pass
reaches REVIEW on all tasks passing
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago Changed · +26 lines 90c8876d0137
- 15d ago Changed · -27 lines · -21 tokens per session 7efb4b879c4a
- 17d ago Changed · -114 lines 7ab18a12f719
- 1mo ago Changed · +2 lines 82461db8b9d2
- 1mo ago First seen · 410 lines · 92 tokens per session scan A 0fcddb9cd0b1
pocket-closing is a skill published in the GitHub repository rfxlamia/pocketto (6 stars, last pushed 7d ago), licensed MIT. It adds 71 tokens to every session and 5,310 once invoked, about $0.0003 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-31.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…