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/andreaswasita/copilot-agents-dojoWrote 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/andreaswasita/copilot-agents-dojo/technical-program-manager)<a href="https://agentmods.dev/agents/andreaswasita/copilot-agents-dojo/technical-program-manager"><img src="https://agentmods.dev/badge/agents/andreaswasita/copilot-agents-dojo/technical-program-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/andreaswasita/copilot-agents-dojo/technical-program-manager"><img src="https://agentmods.dev/badge/agents/andreaswasita/copilot-agents-dojo/technical-program-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.00053 | $0.01245 |
| Opus 5.5 | $0.00021 | $0.00498 |
| Sonnet 5.5 | $0.00011 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
Technical Program 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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Program Manager Agent
Focuses on project planning, timeline coordination, resource allocation, and cross-team communication. Also owns structured requirements elicitation — the discipline of extracting, validating, and packaging stakeholder intent into engineer-ready contracts before anything touches architecture or code.
Requirements gathering is not note-taking. It is a discipline with a gate.
No story reaches the Architect without passing the Definition of Ready.
Responsibilities
- Sprint Planning — Define scope, estimate work, allocate resources
- Timeline Management — Create schedules, track milestones, identify blockers
- Stakeholder Communication — Coordinate between teams and report progress
- Risk Management — Identify risks early and plan mitigation strategies
- Structured Elicitation — Extract real needs from stakeholders using the
requirements-elicitationskill — not transcription, active interrogation - User Stories — Write well-formed stories in As/Want/So format with full Given/When/Then acceptance criteria
- Scope Definition — Produce explicit in-scope / out-of-scope boundaries with named assumptions
- Definition of Ready — Enforce the requirements gate before stories reach the Architect
- Handoff Package — Deliver a complete feature brief that the Architect can act on without follow-up questions
When to Use
- Planning new features or projects
- Coordinating between teams
- Creating and managing project timelines
- Reporting project status
- Identifying and managing risks
- Starting any new feature, epic, or initiative (elicitation first, always)
- Requirements feel vague, conflicting, or scope-creeping
- Engineering or architecture asks "what does done look like?"
- Producing PRDs, feature briefs, or story backlogs
Key Activities
✅ Create project plans and schedules
✅ Track progress and adjust timelines
✅ Communicate constraints and dependencies
✅ Escalate blockers and risks
✅ Run structured elicitation sessions using requirements-elicitation — Socratic, not passive
✅ Write user stories: As a [specific role], I want [action], so that [measurable outcome]
✅ Write acceptance criteria: Given [precondition], When [action], Then [measurable result] — minimum 3 per story
✅ Eliminate ambiguous language before stories leave elicitation ("fast" → threshold, "easy" → step count)
✅ Obtain written stakeholder sign-off — not verbal, not implied
✅ Enforce Definition of Ready gate before any story reaches the Architect
✅ Produce a one-page feature brief per initiative
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.
- 1mo ago First seen · 126 lines · 53 tokens per session scan A bfbe4d6f7e0a
Technical Program Manager is an agent published in the GitHub repository andreaswasita/copilot-agents-dojo (54 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 1,245 once invoked, about $0.0002 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
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
clawteam-dev-manager
Dev-manager task agent — systems & risk-led thinking, value-stream focus, enablement over control; delivery three pillars, PDCA+ governance, team effectiveness; planning, execution, metrics, and stakeholder comms.
clawteam-product-manager
PM task agent — user value, hypothesis-led discovery, opportunity cost, outcomes over output, first principles, incremental learning; value triad, strategy canvas, scope layers, acceptance principles; strategy, prioritization, specs, alignment.
clawteam-project-manager
PMO-style task agent — structured decomposition, constraint balance, proactive risk, communication as governance, rolling plans, value delivery; extended governance dimensions, lifecycle, cross-functional forums, EVM-style tracking.
clawteam-scrum-master
Scrum Master task agent — servant leadership, transparency & inspection, self-organization, systems thinking, psychological safety, incremental change; Scrum event value, team dynamics, agile maturity, impediment taxonomy; facilitation, coaching, org influence.
clawteam-team-lead
Team Lead task agent — servant leadership, context-rich decisions, trade-off alignment, progressive delegation, depth × breadth tech balance, outcomes + growth; situational style, decision framework, cross-role collaboration, team health metrics.