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 integrationgit 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/integration)<a href="https://agentmods.dev/skills/datit309/supergraph/integration"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/integration/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/integration"><img src="https://agentmods.dev/badge/skills/datit309/supergraph/integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 39 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 45 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 40 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 42 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 43 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00956 |
| Opus 5.5 | $0.00011 | $0.00382 |
| Sonnet 5.5 | $0.00005 | $0.00191 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
integration 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/supergraph:integration
Integration + e2e tests. Validates modules work together. Run AFTER unit tests pass.
Usage
/supergraph:integration | plan auth-login | plan auth-login task 3
Prerequisites
- Unit tests passing (
$TEST_CMDgreen) /supergraph:fixcompleted
Steps
0. Announce
"🔗 /supergraph:integration — running integration and e2e tests..."
1. Get Commands
Read from plan ## Environment Context or .supergraph-env. Missing → STOP, run /supergraph:scan first.
2. Verify Unit Tests Pass
$TEST_CMD
If unit tests FAIL → STOP: "Unit tests must pass before integration. Run /supergraph:fix first."
3. Detect Integration Setup
Check for integration configuration:
| Config | Command |
|---|---|
jest.integration.config.js |
npx jest --config jest.integration.config.js |
vitest.integration.config.ts |
npx vitest --config vitest.integration.config.ts |
pytest.ini with [integration] or -m integration |
pytest -m integration |
cypress.config.js / cypress.config.ts |
npx cypress run |
docker-compose.test.yml |
docker compose -f docker-compose.test.yml up --abort-on-container-exit |
*.integration.test.ts / *.integration.spec.ts pattern |
npx jest --testPathPattern="integration" |
If none found → skip: "No integration/e2e config found — skipping."
4. Run Integration Tests
Max 3 retries. On failure:
4b. Serena (optional): See serena/SKILL.md:Setup — find_referencing_symbols/get_diagnostics_for_file per failing module to surface mismatches. Skip if unavailable.
Trace failure to source module, fix, re-run.
5. Run E2E & Full-Stack QA Automation
- QA Matrix Generation: Generate or verify ISTQB QA matrix coverage (
docs/qa/test-matrix-<feature>.md) covering Happy path, Sad path, Boundary, Network 500 error injection, Auth/RBAC, and IDOR (scaffold viabash plugins/supergraph/skills/browser-agent/scripts/init-qa.sh matrix <feature> [ui|api|fullstack]). - Web/Frontend Projects: ALWAYS automatically invoke
/supergraph:browser-agentto run autonomous user-flow tests via native Rust CDP (anti-bot bypass, zero Playwright). - Backend / API Services: Verify API endpoint schemas, response codes, DB state integrity, and error sanitization.
- Execution: Run automated test cases via
agent-browseror project e2e test script. Max 2 retries (e2e is inherently flaky). Annotate flaky tests — do not block merge on known-flaky external network tests.
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.
- 3d ago Changed · +1 lines e997355fd1cb
- 19d ago Changed · +1 lines 044422513120
- 1mo ago First seen · 82 lines · 27 tokens per session scan A 376e10e0dce7
integration is a skill published in the GitHub repository datit309/supergraph (21 stars, last pushed yesterday), licensed MIT. It adds 27 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
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-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…
xcode-testing-workflow
Guide Swift Testing, XCTest, XCUITest, XCUIAutomation-oriented mechanics, code coverage, xctestplan matrices, accessibility-verification follow-through, test filtering, retries, diagnostics, and test-specific fallback work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and…
playwright-skill
Current Playwright (1.64) patterns for writing, debugging, and scaling reliable test suites. Use for any Playwright task, even ones you think you know, because the guides cover APIs and CLI flags newer than most training data. Covers writing or fixing tests, locators, a failing or flaky test, a trace.zip or error…
playwright-core
Battle-tested Playwright patterns for writing and debugging reliable E2E, API, component, visual, accessibility, and security tests. Use when you need locator strategy, assertions, fixtures, network mocking, auth flows, trace debugging, or framework recipes for React, Next.js, Vue, and Angular. TypeScript and…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.