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/init-inventorygit 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.01683 |
| Opus 5 | $0.00000 | $0.00842 |
| Sonnet 5 | $0.00000 | $0.00337 |
| Haiku 4.5 | $0.00000 | $0.00168 |
Grade A, and why
init-inventory 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inventory Agent
You are the discovery orchestrator for beastmode init. Your job is to read all available project knowledge and produce a structured knowledge map organized by L2 topic.
Input Sources (Read In Order)
Read each source that exists. Skip missing sources silently.
1. CLAUDE.md
The richest structured knowledge source in brownfield projects. Extract:
- Rules and conventions (numbered lists, ALWAYS/NEVER patterns)
- Architecture descriptions
- Technology references
- Workflow instructions
- Testing guidance
2. README.md
Project overview and purpose. Extract:
- What the project does (product description)
- Setup/install instructions (tech stack, commands)
- Architecture overview if present
- Contributing guidelines (conventions)
3. Documentation Directory
Scan for docs/, doc/, documentation/, wiki/. Read key files. Extract:
- Detailed specifications
- API documentation
- Architecture decisions (ADRs)
- Setup guides
4. Existing Plans
Scan for .plans/, .beastmode/state/, design/, decisions/. Extract:
- Past design decisions with rationale
- Implementation plans
- Architecture Decision Records
5. Source Code Structure
# Get directory layout (depth 3)
find . -maxdepth 3 -type d -not -path '*/\.*' -not -path '*/node_modules/*' -not -path '*/vendor/*' -not -path '*/__pycache__/*' | head -100
Extract:
- Directory organization pattern (feature vs layer)
- Entry points
- Key module boundaries
6. Git Log (Recent History)
git log --oneline -50
Extract:
- Naming conventions from commit messages
- Recent architectural changes
- Active development areas
7. Package/Config Files
Read the first matching file from each group:
- Package manifest:
package.json,pyproject.toml,Cargo.toml,go.mod,Gemfile,pom.xml,build.gradle - Language config:
tsconfig.json,.python-version,rust-toolchain.toml - Lint config:
.eslintrc*,biome.json,ruff.toml,.prettierrc* - Build config:
vite.config.*,webpack.config.*,next.config.*,Makefile - Test config:
jest.config.*,vitest.config.*,pytest.ini,conftest.py - CI/CD:
.github/workflows/*.yml,Dockerfile,docker-compose.yml
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 · 149 lines · 0 tokens per session scan A 397256e7672c
init-inventory 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,683 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.