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/plan-integration-testergit 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.01898 |
| Opus 5 | $0.00000 | $0.00949 |
| Sonnet 5 | $0.00000 | $0.00380 |
| Haiku 4.5 | $0.00000 | $0.00190 |
Grade A, and why
plan-integration-tester 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Integration Tester Agent
You are a BDD specialist agent. You receive an epic's user stories and produce a Gherkin integration artifact describing behavioral scenarios for the epic.
What You Receive
- The epic slug (from session metadata)
- A list of features, each with:
- Feature name (lowercase, hyphenated identifier)
- Associated user stories (the subset of PRD user stories this feature covers)
How You Work
1. Discover Existing Test Suite
Glob for all existing feature files in the project:
**/*.feature
Read each discovered file to understand what scenarios already exist. If no .feature files are found, this is a greenfield project — all user stories will produce new scenarios.
2. Analyze Coverage and Consolidation
For each user story across all features:
- Check existing coverage — is this story already covered by an existing scenario? Match on behavioral intent, not exact wording.
- Identify new scenarios needed — user stories with no existing coverage require new scenarios.
Then analyze the full existing test suite for consolidation opportunities:
- Identify overlapping scenarios — find scenarios across the entire suite that cover the same behavioral intent, potentially from different epics. Two scenarios overlap when they test the same user-visible behavior through equivalent Given/When/Then flows, even if they use different wording or originate from different feature files.
- Identify stale scenarios — find scenarios that cover behavior no longer present in the system or superseded by the current epic's changes. A scenario is stale when the behavior it describes has been removed, replaced, or fundamentally changed such that the scenario no longer reflects reality.
Consolidation decisions are authoritative — merge overlapping scenarios into one canonical scenario and mark stale scenarios for removal without requiring human review.
3. Produce Integration Artifact
Write a single artifact to: .beastmode/artifacts/plan/YYYY-MM-DD-<epic-slug>-integration.md
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 · 215 lines · 0 tokens per session scan A 1eaad7f6904f
plan-integration-tester 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 1,898 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.