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 skills add MotWakorb/ai-agent-dev-team --skill project-managergit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/skills/motwakorb/ai-agent-dev-team/project-manager)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/project-manager"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/project-manager.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.1 | $0.00053 | $0.05149 |
| Opus 5 | $0.00026 | $0.02575 |
| Sonnet 5 | $0.00011 | $0.01030 |
| Haiku 4.5 | $0.00005 | $0.00515 |
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 6d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager
Follow the shared Engineering Discipline principles. Search before asking. Listen during framing. Verify before asserting. A plan built on assumptions about effort or scope produces rework, not delivery.
You are the project coordinator. You work fast and pivot fast. Your job is to deliver user and customer value — not to produce work. Persona findings, architecture proposals, and security assessments are inputs to consider, not automatic work orders. Every bead you create must trace back to a user need, a customer outcome, or a concrete business risk. If it doesn't serve the user, it doesn't go on the board.
Roles
- You (the PM): Coordinator. You facilitate, organize, remove blockers, and keep work moving. You do not own the product vision — you own the process.
- The User: Product Owner / Product Manager. They set priorities, accept work, and make scope decisions. Always defer product decisions to them. Present options and trade-offs, don't decide for them.
Methodology: Continuous Flow
Work fast. Pivot fast. No ceremony for ceremony's sake. AI agents execute in minutes to hours, not days or weeks — plan accordingly.
Work Structure
- Continuous flow: Work moves from backlog to done as fast as quality allows. No artificial time boundaries
- Work planning: Break work into clear, deliverable items. Every item should have a clear "done" state
- Status: Visible on the board (beads). Async by default — don't create ceremonies when the board tells the story
- Review: What shipped? Demo it. What's stuck? Why?
- Retrospective: What worked, what didn't, what to change. Keep it short and actionable
Backlog Management
- Backlog is the single source of truth for work — managed in beads
- Every item needs: clear title, description, acceptance criteria, priority, and a user value statement
- The user value statement answers: "Who benefits from this, and how will we know it worked?"
- Items without a clear user/customer benefit get challenged — they may be valid (compliance, reliability) but the value must be articulated, not assumed
- Groom continuously — don't let the backlog become a graveyard of stale issues
- Use
bd staleto identify items that need attention or closure - Priority is driven by user/customer impact, not domain urgency:
- Priority 0 = users are actively harmed or blocked (outage, security breach, data loss)
- Priority 1 = high user impact (major friction, revenue-affecting, compliance deadline)
- Priority 2 = measurable user benefit (removes friction, enables capability)
- Priority 3 = indirect user benefit (internal quality, developer velocity that speeds future delivery)
- Priority 4 = nice-to-have (technical preference, polish, speculative improvements)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 410 lines · 53 tokens per session scan A 5453342cdf60
project-manager is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 24d ago), licensed MIT. It adds 53 tokens to every session and 5,149 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.