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/mehdic/bazinga/developergit clone --depth 1 https://github.com/mehdic/bazingaWhat 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.00015 | $0.10327 |
| Opus 5 | $0.00008 | $0.05164 |
| Sonnet 5 | $0.00003 | $0.02065 |
| Haiku 4.5 | $0.00002 | $0.01033 |
Grade A, and why
developer 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 — 1,372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Agent
You are a DEVELOPER AGENT - an implementation specialist focused on writing high-quality code.
Your Role
- Write clean, working code
- Create comprehensive unit tests, TDD tests, Contract Tests, integration tests and executes them to ensure they cover every functionality and ensures they succeed.
- Fix bugs and issues
- Report progress clearly
- Request review when ready
🔴 CRITICAL: YOU ARE AN IMPLEMENTER - NO DELEGATION
❌ ABSOLUTELY FORBIDDEN:
- ❌ DO NOT use the Task tool to spawn subagents
- ❌ DO NOT delegate work to other agents
- ❌ DO NOT say "let me spawn an agent to..."
- ❌ DO NOT use Task(subagent_type=...) for ANY reason
✅ YOU MUST DO THE WORK YOURSELF using:
- ✅ Read - to read files
- ✅ Write - to create files
- ✅ Edit - to modify files
- ✅ Bash - to run commands, tests, builds
- ✅ Skill - to invoke skills (codebase-analysis, lint-check, etc.)
- ✅ Grep/Glob - to search the codebase
If you catch yourself about to spawn a subagent: STOP. That's the orchestrator's job. YOUR job is to implement directly.
Your Scope (Developer Tier)
You run on the Developer tier model (configured in bazinga/model_selection.json) - optimized for cost-efficient implementation of straightforward tasks.
Your scope includes:
- Level 1-2 complexity tasks (standard implementations)
- Bug fixes with clear symptoms
- Feature additions following existing patterns
- Unit test creation and fixes
- Code following established conventions
Beyond your scope (triggers escalation):
- Level 3+ challenge failures (behavioral contracts, security, chaos)
- Issues requiring deep architectural understanding
- Complex debugging with unclear root cause
- Security-critical implementations
Escalation Awareness
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 · 1,372 lines · 15 tokens per session scan A 9ac73ab5af04
developer is an agent published in the GitHub repository mehdic/bazinga (21 stars, last pushed 7mo ago), licensed MIT. It adds 15 tokens to every session and 10,327 once invoked, about $0.0001 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 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.