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 equinor/fusion-skills --skill fusion-issue-task-planninggit clone --depth 1 https://github.com/equinor/fusion-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/equinor/fusion-skills/fusion-issue-task-planning)<a href="https://agentmods.dev/skills/equinor/fusion-skills/fusion-issue-task-planning"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-issue-task-planning/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/equinor/fusion-skills/fusion-issue-task-planning"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-issue-task-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00027 | $0.02042 |
| Opus 5 | $0.00014 | $0.01021 |
| Sonnet 5 | $0.00005 | $0.00408 |
| Haiku 4.5 | $0.00003 | $0.00204 |
Grade A, and why
fusion-issue-task-planning 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 9d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Story Task Planning
Experimental caveat
This skill is experimental and not yet stable. Behavior, structure, and outputs may change between versions.
When to use
Use this skill when you need an actionable task plan for a User Story issue before implementation.
Typical triggers:
- "plan tasks for #123"
- "break this story into steps"
- "create task issue drafts from this user story"
When not to use
Do not use this skill for direct code implementation, PR review, or GitHub mutations without explicit confirmation.
Required inputs
- Target issue reference (
owner/repo#numberor URL) - Desired planning depth (
minimal,standard,detailed) - Run mode (
draft-only,draft+publish-ready, orpublish-now)
If missing inputs block planning, ask up to 3 focused follow-up questions from assets/follow-up-questions.md.
Defaults
- Planning depth:
standard - Run mode:
draft-only - Publish behavior: explicit same-turn confirmation required before any mutation
Tool format
- Tool names follow
<mcp_server>::<tool>(example:mcp_github::sub_issue_write).
Instructions
Execute in order and state assumptions explicitly.
- Probe preferred skills and classify drafting mode
orchestrated: bothfusion-issue-authoringandfusion-issue-author-taskavailable; full workflow with explicit publish gates handled by the orchestrator.direct-subordinate: onlyfusion-issue-author-taskavailable; operate in draft-only mode using its templates and safeguards, do not perform any GitHub mutations, and surface drafts plus clear instructions for how an orchestrator or user should publish them.inline: neither available; stay in draft-only mode, generate task drafts with a minimal built-in structure (Title,Problem,Scope,Acceptance criteria mapping,Verification,Dependencies), and avoid direct references to another skill'sassets/files.- Prefer
fusion-issue-author-taskwhenever it is available; do not bypass it with direct cross-skill file references. - Never stop due to missing preferred skills; degrade gracefully.
What ships with it
4 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.
- 9d ago First seen · 177 lines · 27 tokens per session scan A 6594ec572035
fusion-issue-task-planning is a skill published in the GitHub repository equinor/fusion-skills (1 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 2,042 once invoked, about $0.0001 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.