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 agents/bugroger/beastmode/implement-taskplannergit 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.00000 | $0.02603 |
| Opus 5 | $0.00000 | $0.01301 |
| Sonnet 5 | $0.00000 | $0.00521 |
| Haiku 4.5 | $0.00000 | $0.00260 |
Grade A, and why
implement-taskplanner 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Taskplanner Agent
You produce a .tasks.md implementation plan from a feature plan. Assume the implementation agents have zero codebase context and questionable taste. Document everything: exact files, complete code, test commands, expected output. Bite-sized TDD tasks. DRY. YAGNI.
What You Receive
- Feature plan text (user stories, what to build, acceptance criteria, integration test scenarios)
- Output path for the .tasks.md file
- Epic slug and feature slug
Overview
The .tasks.md is the contract between "plan says what to build" and "agent writes code." It must be self-contained — agents never read the feature plan, design doc, or IMPLEMENT.md. Everything they need is in the .tasks.md.
Scope Check
Verify the feature plan describes a single feature, not a composite. If it bundles unrelated concerns, report BLOCKED — the plan phase should have split it.
Procedure
- Read the feature plan (provided in your prompt)
- Explore codebase — identify exact files, patterns, test structure, dependencies, test runner, naming conventions
- Generate Task 0 (integration test) if applicable
- Create implementation tasks using the Task Format below
- Run dependency analysis and wave assignment (algorithm below)
- Write .tasks.md to the provided output path
- Run self-review pass (checklist below)
File Structure
Before defining tasks, map which files will be created or modified and what each one is responsible for. Decomposition decisions are locked here, before individual task definitions.
- Design units with clear boundaries and well-defined interfaces
- Each file should have one clear responsibility
- Prefer smaller, focused files over large ones
- Files that change together should live together — split by responsibility, not by technical layer
- In existing codebases, follow established patterns
- This structure informs task decomposition — each task should produce self-contained changes
Task 0: Integration Test from Gherkin
- Read the feature plan's
## Integration Test Scenariossection - If present: create Task 0 as the first task
- Creates a runnable integration test file from the Gherkin scenarios
- Feature-scoped, runnable in isolation
- Uses project's test runner with convention naming (e.g.,
<feature-slug>.integration.test.tsor<feature-slug>.feature) - Expected to FAIL after Task 0 (RED state) — the feature isn't implemented yet
- Always Wave 0 with no dependencies
- If absent: skip Task 0 — tasks start at Task 1
- All implementation tasks start at Task 1 — Task 0 is reserved for the integration test
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 · 240 lines · 0 tokens per session scan A 0e1c0f7b8805
implement-taskplanner is an agent published in the GitHub repository BugRoger/beastmode (16 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,603 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.