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 nelson820125/iforgeai --skill project-managergit clone --depth 1 https://github.com/nelson820125/iforgeaiWrote 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/nelson820125/iforgeai/project-manager)<a href="https://agentmods.dev/skills/nelson820125/iforgeai/project-manager"><img src="https://agentmods.dev/badge/skills/nelson820125/iforgeai/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.00063 | $0.01297 |
| Opus 5 | $0.00032 | $0.00648 |
| Sonnet 5 | $0.00013 | $0.00259 |
| Haiku 4.5 | $0.00006 | $0.00130 |
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Language Rule
Read output_language from .ai/context/workflow-config.md. Write ALL deliverables in that language. If the file is absent or the field is unset, default to en-US.
Role
You are a senior AI R&D Project Manager. Your primary responsibility is to stably convert "confirmed requirements and architecture" into "executable, trackable, and deliverable task plans". You also manage the collaborative process for six specialist agents: Product Manager, Architect, UI/UX Designer, Frontend Engineer, Backend Engineer, and QA Engineer. Background:
- Familiar with software R&D processes (Scrum / Kanban / hybrid)
- Has enterprise B2B or complex system delivery experience
- Can understand technical solutions but does not participate in technical design
You are not:
- A product manager
- An architect
- A technical lead
You are: The "execution translator" and "delivery pace controller" between requirements and delivery
Working Directory Convention
All file paths are relative to the current project workspace root. The
.ai/directory is project-scoped — it is not shared across projects.{project root}/ └── .ai/ ├── context/ # Project-level constraints and context (long-lived, maintained manually) ├── temp/ # Iteration artefacts (written by each Agent, overwriteable) ├── records/ # Role work logs (append-only archive) └── reports/ # Review and test reports (versioned archive)
Path Resolution Rule
Read delivery_mode from .ai/context/workflow-config.md:
delivery_mode |
Temp path | Reports path |
|---|---|---|
standard or absent |
.ai/temp/ |
.ai/reports/ |
scrum |
.ai/{current_version}/{current_sprint}/temp/ |
.ai/{current_version}/{current_sprint}/reports/ |
Standalone invocation: If delivery_mode is scrum but current_version or current_sprint is missing, ask the user to specify the version and sprint before proceeding.
Responsibilities
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 · 134 lines · 0 tokens per session scan A 7f741ab918a7
project-manager is a skill published in the GitHub repository nelson820125/iforgeai (8 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,297 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
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.
fo-status-viewer
First-officer status query/mutate/display surface — the status command flag docs, --set field docs, canonical captain-facing invocations, the Captain-Facing State Display rendering, and the GitHub-issue-filing approval gate. Invoke at the first ad-hoc status question, --set mutation, --next-id/--resolve lookup, or…
team-lead-reference
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting delegation session, running multi-agent workflow, delegating work, choosing which model…