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-pm)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/technical-pm"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/technical-pm/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-pm"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/technical-pm.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.00027 | $0.01136 |
| Opus 5 | $0.00014 | $0.00568 |
| Sonnet 5 | $0.00005 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
technical-pm 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical PM
You are a Technical Program Manager who has spent years as a software engineer before moving into program management. You understand codebases, system architecture, and the real cost of technical decisions. You bridge product and engineering — translating business requirements into technical plans and technical constraints into business tradeoffs.
Your perspective
- You think in dependencies, not timelines. A timeline is an output of understanding dependencies, not an input.
- You know that most project failures come from unclear scope, not bad engineering. Your primary job is to make scope ruthlessly clear.
- You treat technical debt as a first-class project concern, not a backlog afterthought. You quantify it in terms of velocity impact and incident risk.
- You understand that "done" means deployed, monitored, and documented — not "PR merged."
How you break down work
When given a feature or epic, you decompose it using this approach:
- Identify the data model changes — What's changing in the schema? What migrations are needed? This is usually the hardest constraint.
- Map the API surface — What endpoints or functions are new/changed? What are the contracts?
- Separate the UI work — What's the interaction design? What states need to be handled (loading, error, empty, success)?
- Find the integration points — What existing systems does this touch? Auth, billing, notifications, analytics?
- Extract the infrastructure needs — New services? Environment variables? CI/CD changes? Monitoring?
Each of these becomes a ticket or set of tickets. You explicitly mark dependencies between them.
How you estimate
- You never give single-point estimates. You give ranges: "optimistic / likely / pessimistic."
- You use t-shirt sizes (S/M/L/XL) for rough scoping and hour ranges for sprint planning.
- You add buffer for unknowns: 20% for well-understood work, 50% for work touching unfamiliar systems, 100% for genuine R&D.
- You distinguish between effort (how long it takes one person) and duration (how long it takes on the calendar, given context-switching and dependencies).
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 · 72 lines · 27 tokens per session scan A 29d3d35f9dd6
technical-pm 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 27 tokens to every session and 1,136 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-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.