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-initgit 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-init)<a href="https://agentmods.dev/skills/rfxlamia/pocketto/pocket-init"><img src="https://agentmods.dev/badge/skills/rfxlamia/pocketto/pocket-init.svg" alt="Measured on agentmods" 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.00085 | $0.01581 |
| Opus 5 | $0.00043 | $0.00790 |
| Sonnet 5 | $0.00017 | $0.00316 |
| Haiku 4.5 | $0.00009 | $0.00158 |
Grade A, and why
pocket-init 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 8d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pocket Init
Standalone onboarding skill. Takes an existing project from zero Pocket context to ready-to-run: a project memory file the agent can rely on, and — only when the user opts in — Pocket Enterprise mode with GitHub templates.
Core principle: Read the project, never guess it. Every claim written to the memory file must come from files actually inspected in this run. User content in an existing memory file is never overwritten.
Use this when: Adopting Pocket in an existing repo, regenerating a stale project guide, or enabling Pocket Enterprise for a team.
Do NOT use when: The project already has a current memory file and enterprise config — there is nothing to initialize. For spec work, go to pocket-grinding.
Invocation
/pocketto:pocket-init [<dir>]
<dir> defaults to the repository root of the current working directory.
Hard Constraints
Step 1: Brownfield scan (read-only)
Inspect the project before writing anything:
- Stack & manifests —
package.json,pyproject.toml,Cargo.toml,go.mod,pom.xml, or equivalent: language, package manager, declared scripts. - Commands — extract the real build / test / lint / typecheck commands from the manifest scripts or CI workflows (
.github/workflows/*). Record them verbatim. - Layout — top-level directories and what lives in each (source, tests, docs, tooling). Keep it to the directories that matter.
- Conventions — formatter/linter configs, commit style visible in
git log --oneline -10, test file naming. - Existing memory files — check for
CLAUDE.mdandAGENTS.md. Note which exist and whether they already contain apocket-initmanaged section or a## Pocket Enterpriseheading.
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.
- 8d ago First seen · 155 lines · 85 tokens per session scan A bbee2ba8865a
pocket-init is a skill published in the GitHub repository rfxlamia/pocketto (5 stars, last pushed 16d ago), licensed MIT. It adds 85 tokens to every session and 1,581 once invoked, about $0.0004 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.
fec-image-generation
A workflow for creating or editing images and diagrams, from posters and product mockups to academic graphics, illustrations, and system maps. For text-heavy technical diagrams, it can use editable sources such as Mermaid, SVG, HTML, or canvas before exporting an image.
esp32-expert
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review…
session-recap
Document Claude Code sessions by extracting knowledge into cross-referenced documentation. Triggers on "recap the session", "summarize the work", or after significant code changes.
knowledge-bank-lookup
Delegates knowledge bank lookups to Explore subagents with reflections-first strategy that learns from past mistakes. Checks /reflections/ directory before documentation to extract documented failures to avoid and proven approaches to apply. Automatically triggers when user mentions services ([project-a], [project-b]…