fusion-issue-authoring

fusion-issue-authoring is a skill for Claude Code, Codex from equinor/fusion-skills. It costs 31 tokens per session (2,262 once invoked), scanned A, original, MIT.

A workflow for turning ideas, bugs, feature requests, or user needs into structured GitHub issues.

In plain words
What is it for?
Use it to classify requests, draft issue content, confirm labels and assignees, review the draft, and publish it safely.
Why use it?
It routes each request to the appropriate issue format and applies shared checks before an issue is changed in GitHub.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to classify requests, draft issue content, confirm labels and assignees, review the draft, and publish it safely.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/equinor/fusion-skills/fusion-issue-authoring
Install

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.

Any agent
npx skills add equinor/fusion-skills --skill fusion-issue-authoring
Clone the repo
git clone --depth 1 https://github.com/equinor/fusion-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for fusion-issue-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-issue-authoring/github.svg)](https://agentmods.dev/skills/equinor/fusion-skills/fusion-issue-authoring)
Your own site
<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.

agentmods 80×15 button for fusion-issue-authoring

Your own site · 80×15
<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>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 9 May 2026
  • Snyk warn 9 May 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash d01f90f03633, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

skills/fusion-issue-authoring/SKILL.md · 194 lines

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 structure
  • agents/feature.agent.md: feature-focused scope and acceptance structure
  • agents/user-story.agent.md: role/workflow/scenario-driven story structure
  • agents/task.agent.md: checklist-first task decomposition and dependency planning
  • agents/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 from fusion-issue-task-planning with 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 @me or exact login.

Read the full file on GitHub · 194 lines

Changes

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.

  1. 8d ago First seen · 194 lines · 31 tokens per session scan A d01f90f03633

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

specstoryai/getspecstory · 126 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens

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.

apache/magpie · 73 tokens