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/bugroger/beastmode/implementnpx skills add BugRoger/beastmode --skill implementgit clone --depth 1 https://github.com/BugRoger/beastmodeWhat 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.00033 | $0.03605 |
| Opus 5 | $0.00016 | $0.01802 |
| Sonnet 5 | $0.00007 | $0.00721 |
| Haiku 4.5 | $0.00003 | $0.00361 |
Grade A, and why
implement 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/implement
Load plan, dispatch subagents per task in wave order, verify completion.
Guiding Principles
- No Plan Mode — this skill operates in normal mode. EnterPlanMode/ExitPlanMode restrict Write/Edit tools and break the workflow.
- Session metadata is the source of truth — the session-start hook injects a metadata block with
epic-id,epic-slug,feature-id,feature-name,feature-slug, parent artifacts, andoutput-target. Use these values verbatim — do NOT re-derive, re-extract, or generate alternatives. - Wave ordering drives sequencing — foundation before consumers; parallel-safe waves dispatch all tasks concurrently; reviews run sequentially after all implementations complete
- Model escalation — start cheap (haiku), escalate on failure (sonnet, then opus). See Reference > Model Escalation.
- Working directory isolation — the CLI provides the working directory; skills don't manage worktrees; each phase commits to the feature branch at checkpoint; merge happens only at /release
- Subagent safety — one agent per task; parallel-safe waves dispatch all tasks simultaneously, non-parallel-safe waves dispatch sequentially; agents commit per task via
git add <files>+git commit; agents must NOT read the plan file, modify files outside their task's file list, or push/switch branches
Phase 1: Execute
Dispatch taskplanner, loop over waves dispatching implementers and reviewers.
1. Dispatch Taskplanner
Spawn the taskplanner agent to produce the .tasks.md:
- Build the prompt — see Reference > Agent Dispatch Templates > Taskplanner
- Spawn:
Agent(subagent_type="beastmode:implement-taskplanner", model="opus", prompt=<built prompt>)
2. Parse Waves
Extract wave numbers and dependencies from the .tasks.md:
- For each task, extract
**Wave:**and**Depends on:**fields - Group tasks by wave number (default wave = 1 if omitted)
- Within each wave, build dependency order from
Depends onfield
3. Wave Loop
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 · 369 lines · 33 tokens per session scan A f69234b329ca
implement is a skill published in the GitHub repository BugRoger/beastmode (16 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 3,605 once invoked, about $0.0002 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
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
agentmail
Use when an agent needs AgentMail CLI email inboxes.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.