agentmods.dev

fusion-skills pr-workflow.instructions.md

fusion-skills pr-workflow.instructions.md is an instructions file for GitHub Copilot from equinor/fusion-skills. It costs 1,235 tokens per session, scanned A, original, MIT.

A set of instructions for managing GitHub issues and pull requests, which are proposed code changes submitted for review. It defines the required steps, questions, checks, templates, and draft files for that process.

In plain words
What is it for?
Use it when preparing, updating, reviewing, or finalising a pull request or issue-related change.
Why use it?
It keeps issue and pull-request work consistent and helps prevent missed decisions, required checks, or project-specific formatting.

Instructions file for GitHub Copilot

not rated 1 3d ago A scan 1,235 tokens original MIT
View the source file equinor/fusion-skills
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.

agentmods
npx agentmods add instructions/equinor/fusion-skills/pr-workflow
Clone the repo
git clone --depth 1 https://github.com/equinor/fusion-skills

Made for: GitHub Copilot.

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-skills pr-workflow.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/equinor/fusion-skills/pr-workflow.svg)](https://agentmods.dev/instructions/equinor/fusion-skills/pr-workflow)
Your own site
<a href="https://agentmods.dev/instructions/equinor/fusion-skills/pr-workflow"><img src="https://agentmods.dev/badge/instructions/equinor/fusion-skills/pr-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,235 This file is loaded in full into every session.
When invoked 1,235 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.01235 $0.01235
Opus 5 $0.00617 $0.00617
Sonnet 5 $0.00247 $0.00247
Haiku 4.5 $0.00123 $0.00123

Measured 5d ago against content hash 72c490a66b6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

fusion-skills pr-workflow.instructions.md 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 5d 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.

.github/instructions/pr-workflow.instructions.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pull request workflow instructions

Apply when handling issue/PR workflows: intake, branch/PR prep, updates, finalization.

Required PR flow

  • Use .github/pull_request_template.md as the PR structure.
  • For PR/issue work, ask whether to use git worktree before any other workflow questions (before branch, base branch, PR body, or PR creation steps).
  • Trigger immediately when issue intent detected — #123, issue 123, or GitHub issue URL.
  • Draft PR body in .tmp/ with issue/context-specific names (e.g. .tmp/pr-body-issue-402-issue-automation-reliability.md); edit with user before submission.
  • Don't use generic .tmp/pr-body.md for new PR drafts.
  • Ask which base branch to target.
  • Propose likely default base branch: usually repo default (main). If current branch was created from another (next, feature branch), suggest that instead.
  • Assume head ref is current branch unless user requests otherwise.
  • Ask whether related issues should be linked.
  • Ask whether the PR should be assigned to the user.
  • Ask whether the PR should be opened as draft or ready for review.
  • Create or update the PR body from that temporary file.

Example commands

  • Create PR from draft body file:
    • gh pr create --base <base-branch> --head <current-branch> --title "<title>" --body-file .tmp/pr-body-<issue-or-context>.md --assignee @me
  • Update an existing PR body from draft body file:
    • gh pr edit <pr-number> --body-file .tmp/pr-body-<issue-or-context>.md

Required checks before PR update/create

Code quality

  • Run lint/format checks before commit operations (bun run biome:check; optionally bun run biome:fix first).
  • Check current branch changes and summarize staged/unstaged scope.
  • Check code and docs against CONTRIBUTING.md, contribute/, and relevant .github/instructions/*.instructions.md.
  • Confirm validation commands run.

Changesets

  • Keep changesets single-scope: each .changeset/*.md file must describe one skill/package change only.
  • If multiple skills/packages changed, split into multiple .changeset/*.md files (one entry per file).

Read the full file on GitHub · 111 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. 5d ago First seen · 111 lines · 1,235 tokens per session scan A 72c490a66b6c

Subscribe to this mod's changes

fusion-skills pr-workflow.instructions.md is an instructions file published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 3d ago), licensed MIT. It adds 1,235 tokens to every session, about $0.0062 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.

Git and workflowReleases
Related

Other instructions, from other repositories

planning-with-files AGENTS.md

AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.

OthmanAdi/planning-with-files · 2,236 tokens

openrouter-mcp-multimodal AGENTS.md

AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).

stabgan/openrouter-mcp-multimodal · 793 tokens

OpenMicro AGENTS.md

Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.

stephenleo/OpenMicro · 123 tokens

ai-usagebar CLAUDE.md

Claude Code instructions for akitaonrails/ai-usagebar, covering claude.md, release checklist — must do all of these, hard invariants — never break these, secret-discipline rules (learned the hard way) and live api smoke discipline.

akitaonrails/ai-usagebar · 4,263 tokens

living-manual CLAUDE.md

Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.

dougstanford/living-manual · 1,108 tokens

yandex360-mcp CLAUDE.md

Claude Code instructions for pa1ch/yandex360-mcp, covering claude.md — гайд для ассистента, как устроен релиз (всё автоматически по тегу), процедура релиза (шаги ассистента), гарды and архитектура (кратко).

pa1ch/yandex360-mcp · 1,005 tokens