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-helpgit 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-help)<a href="https://agentmods.dev/skills/rfxlamia/pocketto/pocket-help"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/pocket-help/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-help"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/pocket-help.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.00112 | $0.03026 |
| Opus 5 | $0.00056 | $0.01513 |
| Sonnet 5 | $0.00022 | $0.00605 |
| Haiku 4.5 | $0.00011 | $0.00303 |
Grade A, and why
pocket-help 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 9d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pocket Help
The map of the Pocket ecosystem. Read this first to understand what Pocket is, pick the right skill for the moment, and run the full flow from rough idea to reviewed code — without loading every skill into context.
Core principle: Orient cheaply, then load deep. This skill is a summary and a router. Load an individual skill's SKILL.md only when you reach the stage that uses it. That is the whole point — it preserves the context window for the actual work.
This skill does not replace the detailed skills. It tells you which one to open next.
What Pocket Is
Pocket is a set of skills for systematic, structured development — from a vague idea to shipped, reviewed code. Instead of one agent improvising an entire feature in a single long thread, Pocket breaks the work into bounded stages with explicit gates: explore → specify (BDD) → plan (TDD) → phase → delegate → review.
Each stage produces a concrete artifact (pitch doc → spec → execution plan → phase files → commits → review reports) that the next stage consumes. Gates between stages force confirmation before proceeding, which is what keeps a long build from drifting.
Prerequisites — Pi extensions
On Pi, Pocket's skills call extensions for their core features. Without them, skills hit dead-ends when they try to call advisor(), subagent(), or context7_* tools. Install them once after installing Pocket:
npx pocketto-pi setup-extensions # required
npx pocketto-pi setup-extensions --all # + recommended
npx pocketto-pi doctor # check installed vs missing
| Required | Feature it powers |
|---|---|
pi-mcp-adapter |
context7 — library-aware code generation |
@gotgenes/pi-subagents |
subagent delegation + parallel reviews |
@juicesharp/rpiv-advisor |
advisor — LLM-to-LLM review/escalation gates |
Recommended (with --all): @juicesharp/rpiv-ask-user-question, @tintinweb/pi-tasks, @aliou/pi-processes. Claude Code users get these capabilities from the harness and do not need the Pi extensions.
What ships with it
4 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.
- 9d ago First seen · 184 lines · 112 tokens per session scan A 8571fdac9619
pocket-help is a skill published in the GitHub repository rfxlamia/pocketto (5 stars, last pushed 16d ago), licensed MIT. It adds 112 tokens to every session and 3,026 once invoked, about $0.0006 per session on Opus 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
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.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.