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 agentmods add skills/danielwpz/pokoclaw/skill-installernpx skills add danielwpz/pokoclaw --skill skill-installergit clone --depth 1 https://github.com/danielwpz/pokoclawWrote 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/danielwpz/pokoclaw/skill-installer)<a href="https://agentmods.dev/skills/danielwpz/pokoclaw/skill-installer"><img src="https://agentmods.dev/badge/skills/danielwpz/pokoclaw/skill-installer.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.00059 | $0.01642 |
| Opus 5 | $0.00030 | $0.00821 |
| Sonnet 5 | $0.00012 | $0.00328 |
| Haiku 4.5 | $0.00006 | $0.00164 |
Grade A, and why
skill-installer 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 6d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Installer
Use this skill when the user asks you to install a skill for Pokoclaw, pastes a skill-store install prompt, or pastes a skill-store CLI command.
This skill does not manage commands the user already ran manually in their own terminal. It handles agent-managed installation.
Core Rule
The task is not complete when an external store says "installed". The task is complete only when the skill is installed in a Pokoclaw-discoverable root and passes the acceptance checks below.
Reason: store CLIs can install into their own roots, active workspaces, or agent-specific locations that Pokoclaw does not read.
Acceptance Checks
Always run these checks yourself at the end of the install.
Do this even when you followed a verified reference exactly. Do this even when the external CLI printed "installed" or "done". Do this even when the skill already appeared to be present.
The install is not complete until all checks pass:
- The final target directory is under the selected Pokoclaw root:
- project-local:
<repo>/.agents/skills/<skill-dir> - global:
~/.pokoclaw/skills/<skill-dir>
- project-local:
SKILL.mdexists at the final target.SKILL.mdfrontmatter has non-emptynameanddescription.- The actual skill identity is taken from
SKILL.mdfrontmatter, not only from the store slug or display title. - Setup-relevant files were inspected but not executed.
- Store provenance was preserved when available:
- for global installs, provenance is stored inside the final skill directory;
- for project-local installs, provenance is either stored inside the final skill directory or in a project lock file that remains with the project.
- Temporary install or staging files were cleaned up.
- Any broader environment change was skipped unless the user approved it.
If any acceptance check fails, report the blocker and do not claim the skill is installed for Pokoclaw.
Read References
If the request matches a verified channel, read the matching reference before installing:
What ships with it
3 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.
- 6d ago First seen · 157 lines · 59 tokens per session scan A 9c517d7cef98
skill-installer is a skill published in the GitHub repository danielwpz/pokoclaw (141 stars, last pushed 17d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,642 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…