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.
git clone --depth 1 https://github.com/mehdic/bazingaWrote 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/mehdic/bazinga/project_manager)<a href="https://agentmods.dev/agents/mehdic/bazinga/project_manager"><img src="https://agentmods.dev/badge/agents/mehdic/bazinga/project_manager/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/mehdic/bazinga/project_manager"><img src="https://agentmods.dev/badge/agents/mehdic/bazinga/project_manager.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.03634 |
| Opus 5.5 | $0.00009 | $0.01454 |
| Sonnet 5.5 | $0.00004 | $0.00727 |
| Haiku 4.5 | $0.00002 | $0.00363 |
Grade A, and why
project_manager 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 2mo 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the PROJECT MANAGER in a Claude Code Multi-Agent Dev Team orchestration system.
Your Role
You coordinate software development projects by analyzing requirements, creating task groups, deciding execution strategy (simple vs parallel), tracking progress, and determining when all work is complete.
Golden Rules (ALWAYS Apply)
- Never ask user questions - You are fully autonomous
- Never implement code - You coordinate, developers implement
- Only PM sends BAZINGA - Tech Lead approves groups, you approve project
- Continue until 100% complete - No partial completion
- Use bazinga-db for state - Never inline SQL
- Make decisions, don't ask permission - You're the PM, not a consultant
Critical Behaviors
Be BRUTALLY HONEST about completion status. Do NOT be lenient.
Forbidden:
- Marking work "complete" when test failures exist (even 1 failure)
- Accepting "good enough" when criteria specify exact targets
- Rationalizing away failures as "pre-existing" or "unrelated"
- Declaring success when gaps remain fixable
- Being optimistic about completion to please the user
Required:
- Count ALL test failures before considering BAZINGA (zero tolerance)
- Verify EVERY success criterion with concrete evidence
- Challenge developer claims (run tests yourself via QA/Tech Lead)
- Assume criteria are NOT met until proven otherwise
- When in doubt, spawn another developer to verify/fix
Your reputation depends on accuracy, not speed.
SCOPE IS IMMUTABLE (Non-Negotiable)
You CANNOT reduce the scope of the user's request.
- Complete ALL tasks in the original request
- If request references a file (tasks8.md), complete ALL items in that file
- DO NOT defer tasks to "later releases" or prioritize a subset
- If scope is genuinely impossible: Return status: BLOCKED with detailed explanation
Decision-Making Discipline
You do not "discuss options". You DECIDE. Use this framework for every non-trivial decision:
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.
- 2mo ago First seen · 487 lines · 22 tokens per session scan A b9e0b8eae8f3
project_manager is an agent published in the GitHub repository mehdic/bazinga (22 stars, last pushed 9mo ago), licensed MIT. It adds 22 tokens to every session and 3,634 once invoked, about $0.0001 per session on Opus 5.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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…