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 agentmods add skills/microsoft/hve-core/functional-plannernpx skills add microsoft/hve-core --skill functional-plannergit clone --depth 1 https://github.com/microsoft/hve-coreWhat 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 | $0.00035 | $0.02992 |
| Opus 5 | $0.00017 | $0.01496 |
| Sonnet 5 | $0.00007 | $0.00598 |
| Haiku 4.5 | $0.00003 | $0.00299 |
Grade A, and why
functional-planner 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 2d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Functional Planner
Read-only, platform-agnostic conventions for turning a Product Requirements Document (PRD) into a validated work-item hierarchy that a separate execution pass creates. This skill owns the decomposition core: how a PRD is analyzed across phases, how a candidate hierarchy is validated against a target platform's supported types, which open planning-framework lens shapes the decomposition, and how the plan is handed off. It never creates, updates, transitions, comments on, or links a work item on any platform.
When to Use
Use this skill when planning a work-item hierarchy from a PRD or requirements artifact for a supported platform, ahead of execution:
- PRD-to-work-item planning — map a PRD into a validated Epic/Feature/Story (or Epic/Story/Task) hierarchy for a separate execution pass.
- Hierarchy refinement — reconcile a candidate hierarchy against a platform's supported types and an existing backlog.
For discovery, triage, and execution of the resulting plan, hand off to the backlog-management skill and the Backlog Manager agent. This skill produces planning-only artifacts and stops at a reviewable handoff.
Invocation
When invoked directly as a command, resolve these before Phase 1:
| Argument | Resolution |
|---|---|
| PRD source | The supplied artifact path, folder, attached file, or explicit PRD content. When omitted, fall back only to a concrete PRD source artifact in the active file or current context. |
| Platform | The supplied target platform, or the tracker resolved from workspace context. Determines which per-platform reference applies. |
| Scope | The target project, owner/repo, or project key used for type validation, label or field confirmation, and related-item discovery. |
| Autonomy | The review-gate level for the resulting handoff, defaulting to partial. |
What ships with it
6 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.
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.
- 2d ago First seen · 161 lines · 35 tokens per session scan A 63ef2f04edce
functional-planner is a skill published in the GitHub repository microsoft/hve-core (1,411 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 2,992 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-30.
Other skills, from other repositories
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…