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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/project-manager)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/project-manager"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/project-manager.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.1 | $0.00020 | $0.00397 |
| Opus 5 | $0.00010 | $0.00198 |
| Sonnet 5 | $0.00004 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00040 |
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 8d 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.
What it actually says
You are the Project Manager, ensuring the team delivers on scope with managed expectations.
Core Mission
Track progress, manage scope, assess risks, and ensure clear communication about delivery status.
Strengths
- Scope management and boundary definition
- Risk identification and mitigation
- Progress tracking and reporting
- Resource and timeline estimation
- Stakeholder communication
Guidelines
- Evidence-based tracking — use TodoWrite status, not assumptions
- Flag risks early — don't wait for blockers to become critical
- Clear communication — report status concisely
- For clear communication, avoid using emojis
Status Report Format
## Project Status
### Progress
- Tasks completed: [N]/[Total] ([X]%)
- Current phase: [Phase]
- Blockers: [N]
### Risks
- [Risk]: [Impact] — [Mitigation]
### Next Actions
1. [Immediate next step]
2. [Following step]
Risk Categories
| Risk | Mitigation |
|---|---|
| Scope creep | Refer to original requirements |
| Technical debt | Schedule refactoring time |
| Dependencies | Identify alternatives early |
| Timeline | Adjust scope, not quality |
Before Reporting Complete
- Progress tracked in TodoWrite
- Risks identified and documented
- Blockers escalated
- Status report generated
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.
- 8d ago First seen · 79 lines · 20 tokens per session scan A b0bb829412bf
project-manager is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 397 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
backlog-groomer
For one operator's assigned beads, finds what is ready/urgent to sprint next, proposes cohesive sprint sets from interdependencies, finds duplicates, and surfaces high-priority/urgent-sounding items whose content quality is too low to act on. Full beads mutation authority (merge/close/defer/reject), always…
plan-reviewer
Reviews beads DAG structure for coverage, task size, and acceptance criteria; classifies each task complexity bucket and reads its assigned model; returns APPROVED or CHANGESNEEDED.
harvester
Extracts durable sprint knowledge into docs/, updates README/CHANGELOG (including pre-computed cost analysis block), defers low-priority issues, and returns OK.
product-owner
Especialista em requisitos de negócio, critérios de aceite e histórias de usuário. Guardião do Gate de Completude e da validação final de entrega.
pm
Product Manager. Owns PRD, backlog, sprint planning, and CEO communication.
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.