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 verifygit 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/verify)<a href="https://agentmods.dev/skills/datit309/supergraph/verify"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/verify/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/verify"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/verify.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.00027 | $0.01085 |
| Opus 5.5 | $0.00011 | $0.00434 |
| Sonnet 5.5 | $0.00005 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
verify 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/supergraph:verify
Requires healthy index_status for CBM_PROJECT (see references/codebase-memory-contract.md); then codebase-memory-mcp detect_changes, trace_path, recipes cycles/hubs/bridges/test-gaps. Block on degraded/new cycle/unapproved hub/missing tests.
Fresh verification gate before completion claims.
Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
When to Use
Before saying/implying: done, fixed, passing, clean, ready, complete, works, verified, successful.
Also: before marking Status: completed, committing, PR'ing, accepting agent reports, moving to next phase.
Usage
/supergraph:verify | tests | lint | build | plan auth-login task 2 | claim "login fixed"
Evidence Mapping
| Claim | Required fresh evidence |
|---|---|
| Tests pass | $TEST_CMD exits 0, zero failures |
| Lint clean | $LINT_CMD exits 0, zero errors |
| Build succeeds | $BUILD_CMD exits 0 |
| Bug fixed | Original failing symptom/test now passes |
| Regression covered | RED failed before fix, GREEN passes after |
| TDD complete | RED failure valid, GREEN passes, refactor verified |
| Task completed | Acceptance criteria met + verification commands pass |
| Agent completed | Diff inspected + independent tests/lint |
| Review passed | Reviewer + graph review + tests/lint pass |
| Ready to merge | Tests + lint + build + review PASS |
Steps
0. Announce
"✅ /supergraph:verify — verifying [claim] with fresh evidence..."
1. Identify Claim
Map claim to required proofs from evidence mapping.
2. Select Plan Context (if applicable)
0 plans → skip | 1 → use | >1 → ask | plan <slug> → match.
3. Get Commands
Read from plan ## Environment Context or .supergraph-env (set by /supergraph:scan). Missing → STOP, run scan first.
No command can prove claim → STOP: "Required check is unknown."
3b. Serena sweep (optional): See serena/SKILL.md:Setup — get_diagnostics_for_file per touched file; STOP on type errors before test suite. Skip if SERENA_ACTIVE=false or unavailable.
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 · 107 lines · 27 tokens per session scan A 0ce56c837cc0
verify is a skill published in the GitHub repository datit309/supergraph (21 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 1,085 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
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…
playwright-frontend
For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable data-testid attributes (naming convention, uniqueness in lists, stability rules) for React…
playwright-qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review…
bootstrap-solution
Bootstrap or guide a reproducible .NET solution with explicit F# or C# language choice, SDK selection, project layout, test project setup, and initial validation commands.
testing-lint-workflow
Plan, run, filter, and triage Android tests and lint, including local unit tests, instrumentation and Compose UI test handoffs, Gradle variant tasks, lint configuration, lint baselines, failure explanations, emulator-aware validation routing, and readable next checks.
build-csharp-project
Build or modify idiomatic C# .NET projects using nullable-aware APIs, records/classes, async/task behavior, analyzer conventions, tests, and repo-local validation.