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-developmentgit 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-development)<a href="https://agentmods.dev/skills/rfxlamia/pocketto/pocket-development"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/pocket-development/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-development"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/pocket-development.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.00037 | $0.07106 |
| Opus 5.5 | $0.00015 | $0.02842 |
| Sonnet 5.5 | $0.00007 | $0.01421 |
| Haiku 4.5 | $0.00004 | $0.00711 |
Grade A, and why
pocket-development 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 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.
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 — 468 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pocket Development
Execute an approved Pocket plan one task at a time or in explicitly parallel groups. The main agent coordinates work, runs mechanical checks, and dispatches independent read-only review; implementers own code changes.
Core principle: Every delegation is a contract. The packet is the contract. No packet, no spawn. Read execution-plan/index.md once to understand execution flow and dependencies, then open individual task files (execution-plan/tasks/T*-*.md) on demand when a task is ready to execute.
Core v4 lifecycle boundary
pocket-development is part of the local-first Core role. Core records neutral lifecycle events for approved specs, completed phases, and closed plans. Core does not call gh, does not merge pull requests, and does not close issues. A separately installed, optional adapter may consume durable events after a successful compatibility preflight. Core work and phase completion do not depend on that adapter; unavailable delivery leaves events pending for replay.
The v4 lifecycle commands use --json --contract 3. lifecycle transition commits local state and an event, lifecycle drain replays pending events in revision order without creating events, and lifecycle repair repairs recoverable log.json projection fields without emitting or dispatching an event. Active v3 plans with progress remain on v3; never silently convert their progress.
Startup: Initialize Execution Log
Run this before the first task, every session:
npx -y pocketto-pi log init "<plan_dir>" --json --contract 3
No install step, PATH setup, or shell-specific guard — npx resolves the cross-platform binary and log init is idempotent, so this is safe to run unconditionally every session. Replace <plan_dir> with the folder containing your execution plan (e.g. docs/pocket/plans/2026-05-08-auth-refactor).
- No
log.jsonyet → creates it from the plan files in that directory log.jsonexists but tasks missing → migrates tasks into existing phases (status preserved)log.jsonalready complete → reports "no migration needed" and writes nothing
What ships with it
15 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.
- .skillkit-mode 4 B
- pocket-development.skill 56 KB
- references/code-quality-review.md 5.3 KB
- references/enterprise-reporting.md 1.1 KB
- references/entry-gate.md 7.5 KB
- references/iron-laws.md 6.1 KB
- references/parallel-group.md 12 KB
- references/phase-completion-notes.md 4.0 KB
- references/phase-level-pass.md 20 KB
- references/pocket-packet.md 9.3 KB
- references/review-report-template.md 13 KB
- references/sandwich-prompt.md 5.8 KB
- references/spec-compliance-review.md 4.5 KB
- references/status-handling.md 4.4 KB
- references/two-stage-review.md 20 KB
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 · +2 lines b15391226c09
- 14d ago Changed · -405 lines · -3 tokens per session be32d9c0133e
- 16d ago Changed · -15 lines de5d39e3cea0
- 1mo ago Changed · -2 lines b79a6fa416af
- 1mo ago First seen · 888 lines · 40 tokens per session scan A 699b217f4e67
pocket-development is a skill published in the GitHub repository rfxlamia/pocketto (6 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 7,106 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-31.
Other skills, from other repositories
adhd
Divergent ideation across model families — the same brainstorm, but each cognitive frame is handed to a different model (Claude sub-agent, OpenAI Codex, a cheap third via OpenCode) so the ideas diverge by frame and by model priors at once. Use for open design questions, architecture and API shape, naming, schema…
x-bug2rag
A knowledge-capture tool that turns reusable bug explanations into a local RAG collection, meaning a searchable store of text that an agent can retrieve later. It records the trigger, incorrect implementation, correct implementation, and observable difference.
fec-drawio-studio
An editable workflow for making technical diagrams in draw.io (also called diagrams.net), with the original .drawio file saved alongside exported images or documents. It covers architecture, database, UML, sequence, flow, machine-learning, and code-structure diagrams.
x-dev-rag-call
A local semantic search tool that finds relevant passages in specified Markdown or text files. It uses an embedding model, which represents meaning as numbers, to return the closest passages for a question or plan.
independent-review-loop
Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer…
resolve-dispute
Resolves stuck review findings via a put-up-or-concede exchange. Invoked by the facilitator when a finding survives arbitration without new evidence.