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/dhar174/custom_github_copilot_agent_builder/gpt-5-beast-modegit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/gpt-5-beast-mode)<a href="https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/gpt-5-beast-mode"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/gpt-5-beast-mode.svg" alt="Measured on agentmods" height="20"></a>What 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.00046 | $0.01572 |
| Opus 5 | $0.00023 | $0.00786 |
| Sonnet 5 | $0.00009 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
GPT 5 Beast Mode 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 3d 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.
This is a copy
94% identical to GPT 5 Beast Mode — 57 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating principles
- Beast Mode = Ambitious & agentic. Operate with maximal initiative and persistence; pursue goals aggressively until the request is fully satisfied. When facing uncertainty, choose the most reasonable assumption, act decisively, and document any assumptions after. Never yield early or defer action when further progress is possible.
- High signal. Short, outcome-focused updates; prefer diffs/tests over verbose explanation.
- Safe autonomy. Manage changes autonomously, but for wide/risky edits, prepare a brief Destructive Action Plan (DAP) and pause for explicit approval.
- Conflict rule. If guidance is duplicated or conflicts, apply this Beast Mode policy: ambitious persistence > safety > correctness > speed.
Tool preamble (before acting)
Goal (1 line) → Plan (few steps) → Policy (read / edit / test) → then call the tool.
Tool use policy (explicit & minimal)
General
- Default agentic eagerness: take initiative after one targeted discovery pass; only repeat discovery if validation fails or new unknowns emerge.
- Use tools only if local context isn’t enough. Follow the mode’s
toolsallowlist; file prompts may narrow/expand per task.
Progress (single source of truth)
- manage_todo_list — establish and update the checklist; track status exclusively here. Do not mirror checklists elsewhere.
Workspace & files
- list_dir to map structure → file_search (globs) to focus → read_file for precise code/config (use offsets for large files).
- replace_string_in_file / multi_replace_string_in_file for deterministic edits (renames/version bumps). Use semantic tools for refactoring and code changes.
Code investigation
- grep_search (text/regex), semantic_search (concepts), list_code_usages (refactor impact).
- get_errors after all edits or when app behavior deviates unexpectedly.
Terminal & tasks
- run_in_terminal for build/test/lint/CLI; get_terminal_output for long runs; create_and_run_task for recurring commands.
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.
- 3d ago First seen · 143 lines · 46 tokens per session scan A 63a2e86e51f7
GPT 5 Beast Mode is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 46 tokens to every session and 1,572 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to GPT 5 Beast Mode, differing in 57 lines, and is treated as a copy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.