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-pm-mcpgit 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-pm-mcp)<a href="https://agentmods.dev/skills/equinor/fusion-skills/fusion-pm-mcp"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-pm-mcp/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-pm-mcp"><img src="https://agentmods.dev/badge/skills/equinor/fusion-skills/fusion-pm-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00102 | $0.01507 |
| Opus 5 | $0.00051 | $0.00754 |
| Sonnet 5 | $0.00020 | $0.00301 |
| Haiku 4.5 | $0.00010 | $0.00151 |
Grade A, and why
fusion-pm-mcp 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 11d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fusion PM MCP Setup Guide
When to use
Use when a user asks:
- what Fusion PM MCP is
- how to install/configure it
- how to verify it is working
- how to troubleshoot a failing setup or stale/rate-limited results
Typical triggers:
- "what is fusion pm mcp"
- "help me set up fusion pm mcp"
- "how do I get GitHub issues/PRs into Copilot without hitting rate limits"
When not to use
- Implementing or modifying the
fusion-pm-mcpservice source code — that belongs to the repository itself - General Fusion Framework/docs/EDS/backend-code retrieval — use
fusion-mcp - Authoring, triaging, or reviewing GitHub issues/PRs — use
fusion-issue-authoringor repo-specific review skills once the MCP tools are available - Making destructive environment changes without user confirmation
Required inputs
Collect before proposing setup steps:
- whether a GitHub token is available (
gh auth token, or a PAT withreposcope) — supplied per-request, not stored in config - target client (VS Code is primary)
If details are missing, ask concise follow-up questions first.
Instructions
- Explain what this MCP server provides:
- a caching proxy over the GitHub REST API, exposed as MCP tools, so agents can read project data without hitting GitHub rate limits on every call
- hosted as a managed service — no local infrastructure required for most users
- tools (verify against
tools/list, the server's actual source is the source of truth over any stale doc):api_get_issue,api_get_parent_issue,api_get_child_issues,api_get_issue_comments,api_list_milestones,api_get_milestone,api_upsert_issue,api_close,api_get_metadata_schema,api_get_pull_request,api_get_pr_comments,api_get_pr_reviews,api_get_pr_review,api_get_review_comments,api_resolve_review_comment - responses are cached (default TTL 300s); there is no cache-invalidation tool — stale results clear on their own after the TTL
- Guide user to set up the hosted production server — the only recommended path:
- no Docker, no local clone, no env vars to manage
- VS Code authenticates the MCP connection via Microsoft Entra (Equinor account)
- the caller also supplies their own GitHub token per request via the
X-GitHub-Tokenheader (each user keeps their own identity and rate limit — don't suggest a shared/service token) - use the manual config in
references/vscode-mcp-config.md(no one-click install link is published for this server) - don't suggest local stdio or the full Docker dev stack — those exist only for contributors working on the
fusion-pm-mcpservice itself; point them to that repo'sCONTRIBUTING.mdinstead of embedding setup steps here
- Describe the authentication flow:
- on first tool invocation VS Code prompts sign-in with the Equinor Entra account (controls access to the MCP server itself)
- separately, the
X-GitHub-Tokenheader carries the caller's own GitHub PAT through to the API on every request - both must be valid; a 401 can come from either layer
- Give a validation checklist:
- run
initializeand confirm a successful response - run
tools/listand compare against the actual returned tool names — don't assume a fixed list, the surface has changed before - run one non-destructive
tools/call(e.g.api_list_milestonesorapi_get_issue) and confirm a non-empty result
- run
- Troubleshoot in documented order:
- Unauthenticated / hitting rate limits fast → no
X-GitHub-Tokenheader configured; unauthenticated calls are capped at 60 req/hr 401or repeated sign-in prompts → re-authenticate via VS Code (sign out/in, or reload the MCP server); if that doesn't resolve it, treat it as a setup bug rather than a known transient issue- Results look stale → there is no invalidate-cache tool; results self-clear after the cache TTL (a few minutes)
- Unauthenticated / hitting rate limits fast → no
- When setup fails or the user asks to file a bug, produce a bug report draft from
assets/bug-report-template.md.- default target repository:
equinor/fusion-pm-mcp - include concrete repro steps, expected vs actual behavior, and troubleshooting already attempted
- include non-sensitive environment details only (OS, VS Code version)
- never include GitHub tokens, PATs, or Entra credentials
- default target repository:
- For uncertainty or repo-private constraints, state assumptions explicitly and link to authoritative docs instead of guessing.
What ships with it
3 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.
- 11d ago First seen · 111 lines · 102 tokens per session scan A 8116c06d0f45
fusion-pm-mcp is a skill published in the GitHub repository equinor/fusion-skills (1 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 1,507 once invoked, about $0.0005 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.