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 triagegit 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/triage)<a href="https://agentmods.dev/skills/datit309/supergraph/triage"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/triage/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/triage"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/triage.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.00073 | $0.00853 |
| Opus 5.5 | $0.00029 | $0.00341 |
| Sonnet 5.5 | $0.00015 | $0.00171 |
| Haiku 4.5 | $0.00007 | $0.00085 |
Grade A, and why
triage 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/supergraph:triage
Classify issues with a formal state machine. ready-for-agent is the handoff trigger to the supergraph pipeline.
Announce: "🗂️ /supergraph:triage — classifying issues..."
State Machine
needs-triage
├── enough info → [assign category] → ready-for-agent | ready-for-human
└── missing info → needs-info → [info provided] → ready-for-agent | ready-for-human
ready-for-agent → supergraph:plan pipeline
ready-for-human → manual dev / architectural decision needed
wontfix → closed with reason
Category Roles
| Category | When |
|---|---|
bug |
Observed behavior differs from specified behavior |
enhancement |
New capability or improvement to existing behavior |
question |
Needs clarification before any action |
spike |
Research / proof-of-concept, no production code |
State Roles
| State | Meaning |
|---|---|
needs-triage |
Unreviewed — default for new issues |
needs-info |
Blocked on missing information from reporter |
ready-for-agent |
Fully specified — safe for /supergraph:plan to consume |
ready-for-human |
Needs human judgment (architecture, business decision, security) |
wontfix |
Will not be addressed — reason required |
Triage Workflow
For each issue:
1. Read the issue completely.
2. Assign category — bug / enhancement / question / spike.
3. Check readiness for agent:
A bug is ready-for-agent when:
- Steps to reproduce are clear
- Expected vs actual behavior is stated
- Environment info is present (version, OS, config)
- No architectural decision required
An enhancement is ready-for-agent when:
- Acceptance criteria are defined
- Scope is bounded (not open-ended)
- No design decision blocking implementation
If NOT ready → set needs-info and list exactly what's missing (one question per response).
4. Assign state and apply labels via GitHub CLI:
gh issue edit <number> --add-label "bug,needs-info"
gh issue edit <number> --add-label "enhancement,ready-for-agent"
gh issue edit <number> --add-label "wontfix"
# Add comment explaining state change:
gh issue comment <number> --body "Triage: [reason for state]"
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 First seen · 105 lines · 73 tokens per session scan A 732ab1bbfbed
triage is a skill published in the GitHub repository datit309/supergraph (22 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 853 once invoked, about $0.0003 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
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
chief-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…
incident-management
Runs an operational incident from detection to closed action — declaring it and naming a commander, separating the people restoring service from the people communicating, keeping a timeline as it happens, deciding when it is over, and running a review that produces a small number of changes someone actually completes.…