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 agentmods add skills/datit309/supergraph/executenpx skills add datit309/supergraph --skill executegit clone --depth 1 https://github.com/datit309/supergraphWhat 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 | $0.00026 | $0.01086 |
| Opus 5 | $0.00013 | $0.00543 |
| Sonnet 5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
execute 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 yesterday.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/supergraph:execute
Dispatch plan tasks with TDD. Parallel by default when tasks are independent.
Usage: /supergraph:execute | task N | tasks N,M | from task N | plan auth-login task 2 | plan auth-login sequential
Steps
0. Announce
"I'm using /supergraph:execute to implement this plan."
1. Load Context
/supergraph:scanshould already be done. If.supergraph-envmissing → STOP: "Run/supergraph:scanfirst."- Commands from
.supergraph-env(if present) or plan## Environment Context
2. Select Plan
Count plan files in docs/supergraph/plans/*.md:
| Count | Action |
|---|---|
| 0 | STOP: "Run /supergraph:plan first" |
| 1 | Auto-select |
>1, no plan <slug> arg |
STOP: list plans, ask user |
plan <slug> provided |
Match filename. If >1 match ask. |
Parse task scope: task N, tasks N,M,K, from task N, or all incomplete.
Parse sequential flag → force sequential mode.
3. Critical Review
Read plan before dispatch:
- Has
## Environment Context? - Selected tasks have all required fields (Status, Risk, Dependencies, Files, Acceptance, TDD, Steps, Checkpoint)?
- Commands real, not placeholders? File paths exact?
- Plan-reviewer returned
Approved(or user explicitly approved)?
If missing or not Approved → STOP, dispatch supergraph:plan-reviewer, wait for Approval.
Also check: plan has user approval step (step 11)? If not → ask user: "Plan was not reviewed by you. Proceed anyway? [yes / no]"
Check dependencies: Task X depends on Task Y → is Y Status: completed? If not → STOP.
If any concern: STOP, ask. Never guess.
4. Branch Protection
If main/master → STOP, suggest new branch or worktree. User approves → continue.
5. Determine Execution Mode
| Condition | Mode |
|---|---|
| No file overlap + no dependencies | Parallel (one agent per task) |
| Any dependency/overlap | Sequential |
| Uncertain | Ask user |
6. Dispatch Executor(s)
Shared executor instructions (see serena/SKILL.md:Setup): per task RED→GREEN→REFACTOR→Lint→Format, get_diagnostics_for_file after GREEN, prefer replace_symbol_body/rename_symbol over raw edits. Commit once per task. Max 3 retries.
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.
- yesterday First seen · 97 lines · 26 tokens per session scan A bcdf3f43ec8d
execute is a skill published in the GitHub repository datit309/supergraph (21 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 1,086 once invoked, about $0.0001 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-30.
Other skills, from other repositories
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
migrate
Inventory an existing spec-driven project and apply bounded migrations to jig defaults: report, adopt-layout, rename-decisions, split-slices, slice-to-spec, seed-decisions, and copy-machinery. Use when the user says migrate this project to jig, adopt jig here, this repo already has specs — set up jig, scaffold-init…
adr-workflow
Scaffold, accept, index, and link Architectural Decision Records (ADRs). Use when the user says "write an ADR", "record this decision", "resolve [deferred item] with an ADR", "supersede ADR-NNNN", or otherwise wants to capture a hard-to-reverse decision in docs/decisions/. Also use when a refinement-todo entry needs…
bug-fix
Drive the teeth-gated lifecycle for reported defects: diagnose root cause, prove it, and prevent regression through REPORTED → DIAGNOSING → ROOTCAUSED → FIXING → REVIEWED → DONE, with VERIFIED, ESCALATED, and RESOLVEDONMAIN paths where needed. Auto-fires on fix this bug, debug this, root-cause this, this regressed…
analyze
Cross-artifact consistency report for jig specs — a non-destructive six-category audit at CRITICAL/HIGH/MEDIUM/LOW severity, covering duplication, ambiguity, underspecification, principle violations, coverage gaps, and terminology drift. Auto-triggers when you say analyze this spec, check for inconsistencies, audit…
arch-review
Team baseline for architecture, design-doc, and RFC review — produces summary, strengths, concerns, and open questions. Auto-triggers when you say review this design, review this architecture, review this proposal, review my RFC, poke holes in this proposal, is this design sound, or critique this tech spec. Defers to…