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.
git 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/plugins/rfxlamia/pocketto/marketplace)<a href="https://agentmods.dev/plugins/rfxlamia/pocketto/marketplace"><img src="https://agentmods.dev/badge/plugins/rfxlamia/pocketto/marketplace/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/plugins/rfxlamia/pocketto/marketplace"><img src="https://agentmods.dev/badge/plugins/rfxlamia/pocketto/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pocketto marketplace 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 3d 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.
What it actually says
{
"name": "pocketto",
"owner": {
"name": "rfxlamia",
"url": "https://github.com/rfxlamia"
},
"description": "Pocket-driven development skills for Claude Code",
"version": "4.2.2",
"surface_manifest": "./surfaces.json",
"surfaces": {
"core": "claude/core",
"enterprise": "claude/enterprise"
},
"plugins": [
{
"name": "pocketto",
"source": { "source": "url", "url": "https://github.com/rfxlamia/pocketto.git" },
"description": "Structured subagent delegation, bug hunting, iterative planning, and code review workflows.",
"category": "productivity",
"tags": ["pocket", "development", "delegation", "bug-hunting", "planning", "structured-research"]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 3d ago Changed 6bf1a0836472
- 6d ago Changed 335dcda8fedb
- 8d ago Changed 60f2fb40bcc8
- 10d ago Changed ab344312bf92
- 12d ago Changed · +6 lines b2879d520813
- 1mo ago First seen · 18 lines scan A 1f8c06c26ea2
pocketto marketplace is a plugin published in the GitHub repository rfxlamia/pocketto (6 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
code-craftsmanship
Code quality and software design skills including Clean Code (Robert C. Martin), Refactoring patterns (Martin Fowler), A Philosophy of Software Design (John Ousterhout), The Pragmatic Programmer (Hunt & Thomas), Domain-Driven Design (Eric Evans), Working Effectively with Legacy Code (Michael Feathers), and Google's…
aspark
An agile AI product team for Claude Code — Specify, Plan, Act, Review, Keep. A Product Owner, Designer, Engineering Manager, Reviewer, QA Tester and Release Manager work your feature through a gated delivery loop.
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
review
Code review for a branch, PR, or path — structured output with severity labels and cross-file analysis.
x-dev-pipeline
Structured dev workflow with spec, user-global risk RAG, task breakdown, execution, verify, qa-gate, fix loops, and audits.
great-cto
You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 72 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.