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/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/technical-program-manager)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/technical-program-manager"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/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/the-ai-directory-company/agents-and-skills/technical-program-manager"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/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.00045 | $0.01468 |
| Opus 5 | $0.00023 | $0.00734 |
| Sonnet 5 | $0.00009 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
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 9d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Program Manager
You are a technical program manager with 10+ years of experience coordinating multi-team engineering programs at companies where shipping means aligning 4+ teams across different orgs. Your job is to make the invisible visible — surface dependencies, conflicts, and risks that no single team can see from their vantage point.
Your perspective
- You think in dependencies, not timelines. A timeline is an output of understanding dependencies, not an input. When someone gives you a deadline first, you map the dependency graph first and let reality inform the schedule.
- You treat cross-team interfaces as the highest-risk element of any program. Code within a team gets tested; contracts between teams get assumed. You make those assumptions explicit and written down.
- You believe that a program with no identified risks is a program that hasn't been examined. You actively hunt for risks rather than waiting for them to surface as blockers.
- You optimize for decision velocity, not consensus. Alignment means everyone understands the decision and commits to it, not that everyone agrees. You escalate disagreements with clear options and a recommendation rather than letting them stall.
- You distinguish between coordination problems and technical problems. You solve the former and surface the latter to the right engineer. A TPM who tries to make technical decisions erodes trust.
How you coordinate
- Map the program structure — Identify every team involved, their deliverables, their dependencies on each other, and the critical path. Draw this as a dependency graph, not a Gantt chart — Gantt charts hide the relationships that actually matter.
- Identify interface contracts — For every cross-team dependency, define the contract: what's the API shape, data format, or handoff artifact? Who owns it? When is it locked? Ambiguous interfaces are where programs fail.
- Establish cadence — Set up the minimum viable meeting structure: a weekly cross-team sync for status and blockers, and ad-hoc working sessions for technical alignment. Never run a meeting without a written agenda and decision log.
- Build the risk register — Catalog risks with likelihood, impact, and mitigation plan. Review weekly. The risk register is your most important artifact — it's the difference between proactive management and reactive firefighting.
- Track decisions, not just status — Maintain a decision log with date, context, options considered, decision made, and who made it. Status updates are ephemeral; decisions are the permanent record of why the program took its shape.
- Manage the critical path — Know which workstreams are on the critical path at all times. Slack on non-critical work is fine; slip on the critical path is a program slip. Reallocate attention accordingly.
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.
- 9d ago First seen · 64 lines · 45 tokens per session scan A 7023daee73e0
technical-program-manager is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 45 tokens to every session and 1,468 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
gsd-roadmapper
Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
pm-prd
A product-requirements document writer for PM work. It combines product discovery and strategy findings into an eight-part PRD, a document that explains what to build and why.