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/existential-birds/beagle/write-plannpx skills add existential-birds/beagle --skill write-plangit clone --depth 1 https://github.com/existential-birds/beagleWhat 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 | $0.00170 | $0.09107 |
| Opus 5 | $0.00085 | $0.04554 |
| Sonnet 5 | $0.00034 | $0.01821 |
| Haiku 4.5 | $0.00017 | $0.00911 |
Grade A, and why
write-plan 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 2d 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 — 460 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Plan: Spec Into Implementation Plan
Turn a brainstorm-beagle spec into a comprehensive implementation plan that an engineer (or a downstream agent) can execute task-by-task without re-deriving intent.
The output is a single markdown plan document at .beagle/concepts/<slug>/plan.md, sitting beside the spec in the same concept folder. The plan captures HOW — file structure, task decomposition, exact code, exact commands — while the spec already owns WHAT and WHY.
<hard_gate>
Do NOT start writing the plan until a brainstorm-beagle spec exists at .beagle/concepts/<slug>/spec.md. If one is missing, stop and route the user to brainstorm-beagle first. Skipping the spec produces plans that bake in unexamined assumptions — the spec is the contract this skill plans against.
</hard_gate>
Workflow
Complete these steps in order:
- Locate the spec — find
.beagle/concepts/<slug>/spec.md; if absent, stop and route to brainstorm-beagle - Read the spec — ingest every section; do not paraphrase, do not summarize away requirements
- Read project conventions — scan project conventions (e.g. AGENTS.md or CLAUDE.md, root and nested) for testing, commenting, and architecture rules the plan must respect
- Explore relevant code — read existing files the plan will touch or pattern-match against; do not guess at structure
- Design file structure — map which files will be created or modified before any task is written
- Decompose into tasks — each task is bite-sized (2-5 minute steps), TDD-driven, with exact paths and code
- Self-review — check against the spec, scan for placeholders, verify type consistency (see Self-Review below)
- Optionally run a reviewer pass — only for plans that are long or cover unfamiliar territory. If the agent supports subagents, dispatch a reviewer subagent; otherwise run the same review inline — identical output (see
references/plan-reviewer.md) - Present draft to user — show the draft in chat for review; iterate if needed
- Write to disk — save to
.beagle/concepts/<slug>/plan.mdonly after explicit user approval
What ships with it
2 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.
- 2d ago First seen · 460 lines · 170 tokens per session scan A 1b8732226b6b
write-plan is a skill published in the GitHub repository existential-birds/beagle (79 stars, last pushed 23d ago), licensed Apache-2.0. It adds 170 tokens to every session and 9,107 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-30.
Other skills, from other repositories
portr-cli
Use when an AI agent or harness needs to operate the Portr CLI: authenticate a client, add users to teams, create HTTP/WebSocket/TCP/stub tunnels, run config-defined tunnels, inspect request logs, replay captured requests, or control tunnels through the local app-server API. This skill is compatible with Claude Code…
compliance-scan
Scans a Python AI project for EU AI Act compliance gaps using AIR Blackbox. Use when the user asks to check compliance, scan their code, audit their AI project, or mentions EU AI Act, Articles 9-15, or compliance checking.
add-tool
Add a new MCP tool to this WhatsApp server. Use when asked to expose a new capability, wrap a new bridge endpoint, or add a tool to tools.py or scheduling.py. Covers annotations, the confirm guard, core-set placement, retrieval aliases, and the eval case.
verify-wire-claim
Verify a claim about WhatsApp behaviour before writing it down. Use whenever about to state that a feature works, a flag is enforced, a message was view-once, a poll cap applies, or any assertion about what WhatsApp does. Also use when documenting a finding in docs/protocol-vs-app.md.
deploy
Build, deploy, verify, or roll back this server on the host. Use when asked to ship a change, rebuild a container, update nginx, or diagnose why the service is down. Covers the memory-capped build, the reload-not-restart rule, and the unhealthy-container failure mode.
xiaohongshu-content-workflow
将书籍、文章或主题素材整理为小红书 3:4 图卡、文案和只读合规复核结果；默认只生成，不发布。.