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 itechmeat/llm-code --skill picoclawgit clone --depth 1 https://github.com/itechmeat/llm-codeWrote 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/itechmeat/llm-code/picoclaw)<a href="https://agentmods.dev/skills/itechmeat/llm-code/picoclaw"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/picoclaw/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/itechmeat/llm-code/picoclaw"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/picoclaw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 47 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 53 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00064 | $0.01723 |
| Opus 5.5 | $0.00026 | $0.00689 |
| Sonnet 5.5 | $0.00013 | $0.00345 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
picoclaw 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 1mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PicoClaw
PicoClaw is an ultra-lightweight AI assistant written in Go. This skill is a practical operator playbook for running the CLI, configuring ~/.picoclaw/config.json, and operating gateway + channels.
Links
Quick navigation
- Getting started + common commands:
references/quickstart.md - Config (
model_list, tools, gateway, channels, bindings):references/config.md - Tools (web search, exec guardrails, registries):
references/tools.md - Auth flows (OpenAI OAuth, Google Antigravity OAuth, token):
references/auth.md - Gateway operations (health/ready, cron, heartbeat, voice):
references/gateway.md - Channels (Telegram/Discord/WeCom/Feishu/OneBot/etc):
references/channels.md - Skills management (install/list/remove, channel commands):
references/skills.md - Hook system (observers, interceptors, approvers):
references/hooks.md - Cron scheduling via CLI:
references/cron.md - Migration notes:
references/migration.md - Troubleshooting:
references/troubleshooting.md
When to use
Use when you need to:
- Bootstrap PicoClaw on a host (onboard → config → run)
- Switch providers/models via
model_list - Run the agent in CLI mode or operate
gateway - Enable chat channels (Telegram/Discord/Slack/WeCom/...)
- Send outbound notifications to Microsoft Teams via webhook targets
- Configure tools (web search, exec deny patterns, skills registries)
- Install/remove skills into the workspace
- Use skill channel commands (
/list skills,/use <skill>) - Configure hook system (observers, interceptors, approvers)
- Configure agent bindings (route messages to different agents)
- Schedule recurring jobs (cron)
Recipes
1) Initialize + verify
- Create initial config and workspace templates:
picoclaw onboard
- Verify what’s configured:
picoclaw status
What ships with it
12 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.
- plan.md 1.3 KB
- references/auth.md 1.2 KB
- references/channels.md 5.8 KB
- references/config.md 5.7 KB
- references/cron.md 944 B
- references/gateway.md 3.5 KB
- references/hooks.md 2.7 KB
- references/migration.md 629 B
- references/quickstart.md 1.5 KB
- references/skills.md 1.5 KB
- references/tools.md 4.0 KB
- references/troubleshooting.md 1.7 KB
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.
- 1mo ago First seen · 140 lines · 64 tokens per session scan A fc2f403a8504
picoclaw is a skill published in the GitHub repository itechmeat/llm-code (24 stars, last pushed 24d ago), licensed MIT. It adds 64 tokens to every session and 1,723 once invoked, about $0.0003 per session on Opus 5.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
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…
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.