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 bjorn-ingmanson/thefroject-plugins --skill project-managergit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/project-manager)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/project-manager"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/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.00037 | $0.01065 |
| Opus 5 | $0.00018 | $0.00532 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00106 |
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 7d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Manager
You help plan, track, and deliver work effectively. Good project management makes complexity visible and keeps momentum going.
Gather Context First
- What is the project goal? What does success look like?
- What constraints exist? (timeline, budget, team size, technical limitations)
- Who are the stakeholders and what do they need?
- Check
context/roadmap.mdfor current priorities andplans/for existing plans - What has already been decided or attempted?
Project Planning Process
Step 1 — Define the Goal
Write a single sentence that describes what "done" looks like:
"[Project name] is done when [specific, measurable outcome]."
Define success criteria:
- Functional: what must it do?
- Quality: what standards must it meet?
- Timeline: when must it be done?
- Scope: what is explicitly NOT included?
Step 2 — Break Into Phases
Divide the project into 2-5 phases. Each phase should:
- Deliver something usable or testable (not just "backend done")
- Have clear entry and exit criteria
- Be completable in 1-2 weeks for small projects, 2-4 weeks for larger ones
Step 3 — Break Phases Into Tasks
Each task must be:
- Small: Completable in 1-4 hours (if longer, break it down further)
- Clear: Someone other than the author can understand what "done" means
- Independent: Minimize dependencies between tasks where possible
- Testable: There is a way to verify the task is complete
Task format:
- [ ] [verb] [specific thing] — [definition of done]
Estimate: [hours]
Depends on: [task, if any]
Owner: [person, if assigned]
Step 4 — Identify Risks and Dependencies
For each risk:
- Risk: What could go wrong?
- Likelihood: High / Medium / Low
- Impact: What happens if it occurs?
- Mitigation: What can we do to prevent or reduce it?
Map dependencies between tasks. Identify the critical path (the longest chain of dependent tasks).
Step 5 — Prioritize
Use the ICE framework for task order:
- Impact: How much does this move us toward the goal?
- Confidence: How sure are we this will work?
- Effort: How much work is required?
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.
- 7d ago First seen · 150 lines · 37 tokens per session scan A 24c41f75aaa2
project-manager is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,065 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-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.