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.
/plugin marketplace add rfxlamia/pockettonpx agentmods add plugins/rfxlamia/pocketto/marketplacegit 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.svg" alt="Measured on agentmods" 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 4d 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",
"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.
- 4d ago First seen · 18 lines scan A 1f8c06c26ea2
pocketto marketplace is a plugin published in the GitHub repository rfxlamia/pocketto (5 stars, last pushed 12d ago), 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
swarms
Launch agent teams for any kind of work — coding, writing, diagnosis, and more.
second-brain
Agentic workflow with memory and tribal knowledge. Transforms Claude from goldfish to elephant with persistent knowledge across sessions.
sprint
Orchestrate staged milestones with native subagents on Claude Code or Oh My Pi, plus codex or mimo executors on Claude Code.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
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.
ui-clone-skills
Motion forensics for the animated web. Four jobs against a live URL: decode (analyse motion + build, no code), clone (URL → React + Tailwind), verify (AE/SSIM + motion-parity score vs. an existing impl), extract (raw JSON dump). Extracts real CSS and animation params (GSAP / Framer Motion / Lenis / anime.js) directly…