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-authoringgit 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-authoring)<a href="https://agentmods.dev/skills/equinor/fusion-skills/fusion-issue-authoring"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-issue-authoring/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-authoring"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-issue-authoring.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.00031 | $0.02262 |
| Opus 5 | $0.00015 | $0.01131 |
| Sonnet 5 | $0.00006 | $0.00452 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
fusion-issue-authoring 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 8d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Authoring
Agent modes
This skill uses internal agent modes for type-specific drafting logic:
agents/bug.agent.md: bug-focused issue drafting and triage structureagents/feature.agent.md: feature-focused scope and acceptance structureagents/user-story.agent.md: role/workflow/scenario-driven story structureagents/task.agent.md: checklist-first task decomposition and dependency planningagents/devils-advocate.agent.md: always-on quality collaborator that raises key concerns after classification (moderate mode) and runs a full structured interview when explicitly asked, when scope/criteria gaps are significant, or when invoked fromfusion-issue-task-planningwith two or more architecture-ambiguity signals present (interrogator mode)
Agent modes are activated internally based on issue type classification. Users never reference agent files directly. Shared gates (labels, assignee confirmation, draft review, publish confirmation, and mutation sequencing) remain in this skill.
When to use
Use when turning ideas, bugs, feature requests, or user needs into clear, actionable GitHub issues, and as top-level router for creating and updating issues.
Typical triggers:
- "create an issue"
- "draft a ticket"
- "turn this into a GitHub issue"
- "help me structure this work item"
- "update / maintain / clean up this issue"
- "add this as a sub-issue / set parent issue / link as child"
When not to use
- Implementing code changes
- PR authoring or review
- General research not resulting in an issue draft
- Mutating GitHub state without explicit user confirmation
Required inputs
Collect before publishing:
- Target repository
- Issue intent/context and type (Bug, Feature, User Story, Task)
- Existing issue number/URL when updating
- Repository label set (or confirmation labels are intentionally skipped). Cache full label set per repo for session; filter locally. Prefer host session memory; otherwise
.tmp/cache file (never committed). - Parent/related issue links and dependency direction (sub-issue vs blocking)
- Assignee preference (
@me, specific person, or unassigned). Reuse cached assignee-candidate results; skip searches when user gave@meor exact login.
What ships with it
28 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.
- agents/bug.agent.md 1.0 KB
- agents/devils-advocate.agent.md 6.1 KB
- agents/feature.agent.md 1011 B
- agents/task.agent.md 1.5 KB
- agents/user-story.agent.md 1.1 KB
- assets/graphql/issue_lookup.github.graphql 371 B
- assets/graphql/issue_type_update.github.graphql 215 B
- assets/graphql/issue_types_list.github.graphql 159 B
- assets/graphql/linkage_verify.github.graphql 408 B
- assets/graphql/README.md 2.5 KB
- assets/graphql/sub_issue_remove.github.graphql 201 B
- assets/graphql/sub_issue_reprioritize.github.graphql 260 B
- assets/graphql/sub_issue_write.github.graphql 195 B
- assets/issue-templates/bug.md 378 B
- assets/issue-templates/feature.md 380 B
- assets/issue-templates/task.documentation.md 295 B
- assets/issue-templates/task.md 180 B
- assets/issue-templates/task.planning.md 296 B
- assets/issue-templates/task.research.md 307 B
- assets/issue-templates/task.spec.md 351 B
- assets/issue-templates/task.testing.md 252 B
- assets/issue-templates/task.ux.md 435 B
- assets/issue-templates/user-story.md 306 B
- assets/README.md 932 B
- CHANGELOG.md 10 KB
- references/instructions.md 4.1 KB
- references/mcp-server.md 8.0 KB
- references/questions.md 1.8 KB
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.
- 8d ago First seen · 194 lines · 31 tokens per session scan A d01f90f03633
fusion-issue-authoring is a skill published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 2,262 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.