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 lovelybunch/coconut-skills --skill coconut-skills-creatorgit clone --depth 1 https://github.com/lovelybunch/coconut-skillsWrote 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/lovelybunch/coconut-skills/coconut-skills-creator)<a href="https://agentmods.dev/skills/lovelybunch/coconut-skills/coconut-skills-creator"><img src="https://agentmods.dev/badge/skills/lovelybunch/coconut-skills/coconut-skills-creator/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/lovelybunch/coconut-skills/coconut-skills-creator"><img src="https://agentmods.dev/badge/skills/lovelybunch/coconut-skills/coconut-skills-creator.svg" alt="Reviewed on agentmods" width="80" 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.00185 | $0.02634 |
| Opus 5 | $0.00093 | $0.01317 |
| Sonnet 5 | $0.00037 | $0.00527 |
| Haiku 4.5 | $0.00018 | $0.00263 |
Grade A, and why
coconut-skills-creator 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 12d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coconut Skills Creator
A meta-skill for authoring Coconut skills: single-file SKILL.md documents that run on a Coconut instance — a VM with the nut CLI installed and a .nut/ directory. At runtime the SKILL.md is consumed by Claude Code (or an equivalent agent loop) on that instance, which executes nut subcommands to manipulate tasks, resources, knowledge, context, and third-party connectors.
Your job is to turn a user's description — whether a plain-English goal or a rough step list — into a well-formed SKILL.md that another instance of Claude can read and execute on a Coconut.
What matters is that the generated skill works at runtime — reads the right files, runs the right nut commands, produces the right artifact, and is unambiguous enough that the runtime agent doesn't have to guess. Business-like and efficient is fine. Don't try to preserve anyone's "voice" — optimize for a runtime agent that will read and execute.
What Coconut skills look like
A Coconut skill is fundamentally a prompt with nut commands woven into it. It reads relevant .nut/ files for context, reasons about what to do, takes action by shelling out to nut subcommands, and typically ends by creating a task or notifying a channel. Use direct, instructional language — imperative voice, concrete commands, clear "read first / then do / then report" structure.
Coconut skills are NOT:
- Python packages or bundles with
scripts/andassets/ - Code-generation templates
- Rigid step-by-step scripts with hard-coded branching
They ARE:
- A prompt, opinionated about what to do and which
nutcommands to use, but trusting the runtime agent to adapt
Keep this distinction top of mind — the output is a single markdown file with YAML frontmatter, nothing else.
Workflow
Step 1: Detect the input mode
The user will give you one of two things:
Mode A — Plain-English goal. A description of what the skill should accomplish, without specifying steps. Example: "create a loop that drafts new tasks for me based on my role and memory, avoiding duplicates, and notifies Slack when done." Your job is to fill in the structure: which .nut/ files to read, what the reasoning should look like, which nut commands to emit, what the "done" signal is.
What ships with it
4 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.
- 12d ago First seen · 125 lines · 185 tokens per session scan A f38827fcc249
coconut-skills-creator is a skill published in the GitHub repository lovelybunch/coconut-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 185 tokens to every session and 2,634 once invoked, about $0.0009 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
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…