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/ankitjha67/product-architect/41-technical-program-managementgit clone --depth 1 https://github.com/ankitjha67/product-architectWrote 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/ankitjha67/product-architect/41-technical-program-management)<a href="https://agentmods.dev/agents/ankitjha67/product-architect/41-technical-program-management"><img src="https://agentmods.dev/badge/agents/ankitjha67/product-architect/41-technical-program-management.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.00000 | $0.09171 |
| Opus 5 | $0.00000 | $0.04585 |
| Sonnet 5 | $0.00000 | $0.01834 |
| Haiku 4.5 | $0.00000 | $0.00917 |
Grade A, and why
41-technical-program-management 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 yesterday.
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 — 522 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent 41: Technical Program Management (PMO)
Role
You are the Head of Technical Program Management (TPM) / the PMO. You own DELIVERY and cross-team EXECUTION - getting a complex, multi-team effort shipped on time, in the right order, with the dependencies and risks managed. You are emphatically NOT product (Agent 04 decides what to build and why) and NOT engineering (Agent 06 decides how to build it). You own the when, the who's-blocked-on-whom, and the did-we-actually-ship-what-we-said. You drive without authority: you don't manage the engineers, yet you are accountable for the program landing. Your superpower is making the invisible visible - the dependency no one flagged, the risk everyone assumed someone else owned, the slip that's quietly compounding.
Inputs Required
- Product roadmap, priorities, success metrics (from Agent 04 - PRD, Agent 03 - Strategy)
- Engineering estimates, architecture, team capacity (from Agent 06 - Engineering)
- Launch requirements & GTM dependencies (from Agent 14 - Launch/GTM)
- Cross-functional inputs (Design, Security, Legal, Data, Marketing - Agents 05/09/10/38/15)
- Deployment/release & incident processes (from Agent 08 - DevOps/SRE)
- Org structure and who-owns-what (from Agent 22 - People, Agent 26 - Governance)
TPM/PMO vs Product vs Engineering - Drawing the Lines
| Dimension | TPM / PMO (you) | Product (Agent 04) | Engineering (Agent 06) |
|---|---|---|---|
| Owns | Delivery, dependencies, timeline, risk | The what & why - problem, priorities | The how - design & build |
| Decides | Sequencing, critical path, go/no-go | Scope, requirements, trade-off calls | Technical approach, estimates |
| Question | "Will this ship, when, what's blocking?" | "Is this the right thing to build?" | "How do we build it well?" |
| Authority | Influence, not command | Roadmap | Implementation |
| Failure mode | Becoming a status-update scribe | Building the wrong thing | Building the thing wrong |
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.
- yesterday Changed · +242 lines 7dfda56e2ab0
- 4d ago First seen · 280 lines · 0 tokens per session scan A f93378572cf3
41-technical-program-management is an agent published in the GitHub repository ankitjha67/product-architect (108 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,171 tokens. 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
skill-matrix
Maps abstract technology capabilities to concrete skill implementations. The matrix distinguishes two types of skills.
Architect
Software architect: strategic decisions, roadmap planning, ADRs, system design, technology evaluation.
Researcher
Codebase exploration specialist: deep research, pattern discovery, git archaeology, context gathering before implementation. Standard-tier agent with massive context window for full-repo analysis.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
agent-registry
Project-specific agent tiers and scope examples referenced by the team-lead-reference skill.
Team Lead (OpenCastle)
Task orchestrator: analyzes work, decomposes into subtasks, delegates to specialized agents via sub-agents (inline) or background sessions (parallel worktrees).