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 datit309/supergraph --skill fixgit clone --depth 1 https://github.com/datit309/supergraphWrote 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/datit309/supergraph/fix)<a href="https://agentmods.dev/skills/datit309/supergraph/fix"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/fix/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/datit309/supergraph/fix"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00956 |
| Opus 5.5 | $0.00013 | $0.00382 |
| Sonnet 5.5 | $0.00007 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
fix 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 1mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/supergraph:fix
Plan-aware auto-fix loop. Ensure tests pass, lint clean, format applied, graph risks handled.
Usage
/supergraph:fix | /supergraph:fix plan auth-login | /supergraph:fix plan auth-login task 2
Steps
0. Announce
"🔧 /supergraph:fix — starting auto-fix loop..."
1. Select Plan Context
0 plans → skip | 1 → use | >1 → ask | plan <slug> → match.
Read ## Environment Context, fix scoped task or all in-progress/stuck tasks.
2. Get Commands
Read from plan ## Environment Context or .supergraph-env (set by /supergraph:scan). Missing → STOP, run scan first.
Missing command → skip phase, report as SKIP.
3. Get Changed Files
git diff --name-only && git diff --cached --name-only. Reindex CBM_PROJECT if stale (index_status→index_repository, see references/codebase-memory-contract.md) via codebase-memory-mcp.
3b. Serena pre-loop (optional): See serena/SKILL.md:Setup. If scan not run, call initial_instructions; get_diagnostics_for_file per changed file to catch type errors early. Skip if SERENA_ACTIVE=false or unavailable.
4. Auto-Fix Loop (max 3 iterations)
At iteration start: "🔧 Fix iteration N/3 — running tests..."
| Phase | Action |
|---|---|
| Reproduce | Smallest failing cmd + expected vs actual |
| Tests | Targeted tests else $TEST_CMD; fix source. Dedup: if same HEAD_SHA and last PASS <120s and git diff unchanged, reuse evidence; else rerun fresh (respects verify freshness guard) |
| Serena fix | get_diagnostics_for_file + replace_symbol_body/rename_symbol (see serena/SKILL.md) |
| Format+Lint | $FORMAT_CMD→$LINT_CMD; rerun lint if formatted |
| Graph | Reindex CBM_PROJECT if stale (index_status→index_repository) — respect scan: TTL 10m (skip index_repository if fresh per .supergraph-env), then codebase-memory-mcp recipes cycles/test-gaps/complexity/cross-boundary |
| Decide | All clean→break else continue |
5. Update Plan Status (if plan exists)
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.
- 1mo ago Changed · +9 lines a8ed75060eb7
- 1mo ago First seen · 74 lines · 33 tokens per session scan A 2fe5bdfe8daa
fix is a skill published in the GitHub repository datit309/supergraph (22 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 956 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
diagnose-project
Diagnose .NET SDK, restore, build, test, package, target framework, F# compile-order, C# analyzer, and project-reference failures with concrete next checks.
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
xcode-build-run-workflow
Guide build, run, preview-adjacent, workspace-inspection, diagnostics, toolchain, and guarded mutation work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and the task is primarily about build, run, or project-integrity work rather than testing.
safari-mcp-workflow
Inspect a scoped live site in Safari through Safari Technology Preview's local MCP server. Use for Safari-specific DOM, console, network, screenshot, accessibility, performance, interaction, responsive, or print-media evidence.
xcode-debugger-mcp-workflow
Diagnose a running Apple app through Xcode’s active LLDB debugging session and assess the experimental Xcode 27 lldb-mcp executable. Use when setting breakpoints, inspecting frames or variables, issuing LLDB commands, or distinguishing a usable Xcode debugger session from an unavailable standalone debugger MCP server.