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 cmdaltctr/niftypm-mcp --skill s-niftypmgit clone --depth 1 https://github.com/cmdaltctr/niftypm-mcpWrote 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/cmdaltctr/niftypm-mcp/s-niftypm)<a href="https://agentmods.dev/skills/cmdaltctr/niftypm-mcp/s-niftypm"><img src="https://agentmods.dev/badge/skills/cmdaltctr/niftypm-mcp/s-niftypm.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.00172 | $0.07831 |
| Opus 5 | $0.00086 | $0.03915 |
| Sonnet 5 | $0.00034 | $0.01566 |
| Haiku 4.5 | $0.00017 | $0.00783 |
Grade A, and why
s-niftypm 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
s-niftypm
Reference skill for any AI agent acting as a Project Manager or assistant in NiftyPM. Teaches the NiftyPM hierarchy, best practices, and exact MCP tool sequences for common project management workflows.
NIFTYPM HIERARCHY (CRITICAL — MEMORISE THIS)
Every operation in NiftyPM sits within this hierarchy. All create/list/update calls need parent IDs from the level above:
Workspace
└── Portfolio (subteam) ← create with: niftypm_create_subteam
└── Folder (optional) ← create with: niftypm_create_folder
└── Project ← create with: niftypm_create_project
├── Task List/Group ← create with: niftypm_create_taskgroup
│ └── Task ← create with: niftypm_create_task
│ └── Subtask ← create with: niftypm_create_task (with task_id)
│ └── Checklist ← create with: niftypm_create_checklist + niftypm_create_checklist_items
├── Milestone ← promote a Task List via niftypm_create_milestone
├── Doc ← create with: niftypm_create_document
├── File ← upload with: niftypm_upload_files
├── Discussion ← create messages with: niftypm_create_message
└── Goal ← UI-only at this time
Discovery order (always follow this): List existing → find IDs → create/update.
MANDATORY WORKFLOW RULES
Rule 0: Discover Before You Create
Always list existing resources first. Never assume IDs.
niftypm_list_projects() → find project_id
niftypm_list_taskgroups(project_id="...") → find taskgroup_id
niftypm_list_subteams() → find portfolio_id
Rule 0a: Reconcile Default Task Lists AND Milestones
A newly created or template-based project ALWAYS ships with auto-generated default task lists AND milestones (e.g., "To Do", "In Progress", "Done" for task groups; an unnamed "Untitled List" for milestones). Before you create any custom lists or milestones, you MUST list the existing ones and decide: delete the defaults you won't use, or rename/reuse them.
What ships with it
8 files 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.
- references/niftypm-best-practices.md 3.2 KB
- references/niftypm-project-plan-schema.md 11 KB
- references/niftypm-project-plan-template.json 3.5 KB
- references/niftypm-project-plan.schema.json 8.2 KB
- references/niftypm-tools.md 16 KB
- references/niftypm-workflows.md 16 KB
- references/reverse-sync-workflow.md 4.4 KB
- scripts/reverse-sync.py 7.7 KB runs code
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 · 550 lines · 172 tokens per session scan A 99befdb35716
s-niftypm is a skill published in the GitHub repository cmdaltctr/niftypm-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 172 tokens to every session and 7,831 once invoked, about $0.0009 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
omc-plan
Strategic planning with optional interview workflow.
launch
Shipyard's governed delivery pipeline — converge the mission, synthesize a durable spec, decompose vertical-slice tickets with blocking edges, run the frontier in parallel via team, close with verification, and report with a full decision log. Two entry gates — the yard gate (drydock audit) and the fog gate (an effort…
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
ask-navigator
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it…
ultragoal
Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session.
agtx-sweep
Sweep this conversation into agtx tasks and push them to the kanban board. Use when the user wants to capture, decompose, or hand off conversation results to the agtx board.