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 magnus919/agent-skills --skill technical-program-managementgit clone --depth 1 https://github.com/magnus919/agent-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/skills/magnus919/agent-skills/technical-program-management)<a href="https://agentmods.dev/skills/magnus919/agent-skills/technical-program-management"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/technical-program-management/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/skills/magnus919/agent-skills/technical-program-management"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/technical-program-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00128 | $0.02709 |
| Opus 5 | $0.00064 | $0.01354 |
| Sonnet 5 | $0.00026 | $0.00542 |
| Haiku 4.5 | $0.00013 | $0.00271 |
Grade A, and why
technical-program-management 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Program Management
Program-level control can fail even when every component is on its own track. Use this skill to see and manage the seams, not to replace project managers or product governance.
First move: prove the program boundary
A program is not a larger project: it exists because coordination, shared constraints, or benefits across components require decisions that no component owner can make alone.
Read existing strategy, business case, component plans, dependency records, benefits assumptions, and recent status evidence before creating ceremony. Establish:
- the shared outcome and why the components belong together;
- the senior accountable owner and program decision rights;
- component projects/workstreams, owners, interfaces, and operational recipients;
- expected benefits, benefit owners, measures, baselines, timing, and disbenefits;
- shared capacity, funding, architecture, vendors, environments, and policy constraints;
- the current phase, critical decision, evidence gaps, and stop/revisit conditions.
If the work is one bounded project, route to technical-project-management. If the work is only a collection of unrelated investments, route to product-roadmapping-and-portfolio or strategy-frameworks.
Reference routing
Read only what the current decision requires:
| Situation | Read |
|---|---|
| Program mandate, component map, or shared constraints | Program brief template |
| Integrated status, dependency, risk, or recovery problem | Program control and troubleshooting |
| Benefits, governance, or evidence boundary | Research ledger |
| Benefits dependency mapping, tranche decisions, or disbenefits | Benefits dependency and tranche control |
| Adoption, operating-model change, or benefit drift | Benefits and transformation |
| Integrated control record needs filling | Integrated control template |
| Audience-specific status or decision update | Stakeholder update template |
| Independent assurance or troubled-program intervention | Assurance and intervention |
| One project needs detailed control | technical-project-management |
| Product portfolio or capital-allocation choice | product-roadmapping-and-portfolio or strategy-frameworks |
What ships with it
12 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.
- evals/evals.json 7.8 KB
- README.md 2.4 KB
- references/assurance-and-intervention.md 2.8 KB
- references/benefits-and-transformation.md 2.4 KB
- references/benefits-dependency-and-tranches.md 2.6 KB
- references/program-control.md 2.8 KB
- references/research-ledger.md 4.3 KB
- templates/assurance-review.md 860 B
- templates/benefits-dependency-map.md 671 B
- templates/integrated-control.md 1016 B
- templates/program-brief.md 832 B
- templates/stakeholder-update.md 902 B
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 · 200 lines · 128 tokens per session scan A e221720962ae
technical-program-management is a skill published in the GitHub repository magnus919/agent-skills (76 stars, last pushed yesterday), licensed MIT. It adds 128 tokens to every session and 2,709 once invoked, about $0.0006 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-06.
Other skills, from other repositories
cocoharvest
Decompose an approved plan into parallel workstreams, assign specialist personas, classify stages as HITL or AFK (CocoLens), generate flow.json stages with checkpoints and dual-file state, and create per-stage prompt files. Includes adaptive parallelism, stall detection, shell identity injection, and consecutive…
plan
Enter the Plan phase of CocoBrew. Runs CocoSpec quality gate pre-flight, reads spec.md and discuss.md (if present), invokes Coco native plan mode as a mandatory gate, captures the approved plan to plan.md, creates initial flow.json template, and commits. Must have $spec completed first.
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.
ops-demo
CocoOps demo mode activator — populates .cocoplus/ops/demo/ with realistic mock data and sets cocoplus.toml [demo] enabled = true. Invoked via $ops demo.
ops-dora
CocoOps DORA metrics — computes four DORA-adapted delivery metrics from Snowflake task history and git log. Extends the longitudinal delivery thesis through the skill-native CocoOps thesis workflow. Invoked via $ops dora.
ops-sprint
CocoOps sprint health — computes story velocity, burndown, and completion prediction from git log and sprint window config. Invoked via $ops sprint.