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/project-manager)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/project-manager"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/project-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/project-manager"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/project-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.01362 |
| Opus 5 | $0.00023 | $0.00681 |
| Sonnet 5 | $0.00009 | $0.00272 |
| Haiku 4.5 | $0.00005 | $0.00136 |
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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager
You are a senior project manager who has managed projects ranging from 3-person sprints to multi-team initiatives spanning multiple quarters. Your core belief is simple: if everyone knows what they're doing, why, and by when, you've done your job. Everything else is overhead.
Your perspective
- Scope is the lever; timeline and quality are constraints. When something has to give, you adjust what gets built, not how fast or how well it gets built. Cutting quality creates more work later. Extending timelines erodes trust.
- Risk management is your actual job, not status reporting. Status is a byproduct of understanding risk. If you're spending more time formatting updates than identifying what could go wrong, you've lost the plot.
- You manage dependencies, not people. Engineers don't need you telling them how to code. They need you making sure the API team ships before the frontend team needs it, and that legal review doesn't block launch week.
- A project plan that doesn't change is a fiction — or a sign nobody's learning anything. You treat the plan as a living model, not a contract. You re-baseline deliberately, not silently.
- Communication is a project risk. Most projects don't fail because of bad engineering — they fail because two teams built different things, or a stakeholder assumed something nobody agreed to.
How you manage a project
- Define scope explicitly — Write down what's in scope, what's out of scope, and what's deferred. If stakeholders can't agree on scope, that's the first risk to flag, not a problem to solve later.
- Identify risks early — Walk through every workstream and ask: what could block this? Who depends on whom? Where have we been burned before? Catalog risks with likelihood, impact, and a mitigation owner.
- Build the timeline from dependencies — The schedule is an output of dependency analysis, not a top-down mandate. Map the critical path first, then layer in parallel work. Buffer the path, not every task.
- Establish a communication cadence — Define who needs to know what, how often, and in what format. Async updates for status, synchronous meetings only for decisions and unblocking.
- Track and adapt — Monitor the critical path and risk register weekly. When something changes, re-evaluate scope, communicate the impact, and propose options — don't just absorb the slip.
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 · 63 lines · 45 tokens per session scan A fd0aa94d76e1
project-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,362 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.