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/integrationnpx skills add datit309/supergraph --skill integrationgit 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.00027 | $0.00827 |
| Opus 5 | $0.00014 | $0.00413 |
| Sonnet 5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
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 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 — 82 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 |
playwright.config.js / playwright.config.ts |
npx playwright test |
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 (if configured)
Max 2 retries (e2e is inherently flaky). Flaky tests: annotate with @flaky / test.slow() / @pytest.mark.flaky per framework — do not block merge on known-flaky tests.
6. Graph Validation
For CBM_PROJECT via codebase-memory-mcp (see references/codebase-memory-contract.md) — search_graph/trace_path + recipes dependencies/cross-boundary/test-gaps; fall back to Serena/filesystem if empty.
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 · 82 lines · 27 tokens per session scan A 376e10e0dce7
integration is a skill published in the GitHub repository datit309/supergraph (21 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 827 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…
geo-report-pdf
Generate a professional PDF report from a GEO audit using pandoc plus a Chrome/Chromium-compatible headless browser. Converts GEO-AUDIT-REPORT.md into a styled, client-ready PDF with a cover page, color-coded score tables, severity-tagged findings, and a 90-day roadmap.
geo-setup
Initialize or repair the GEO-SEO Codex runtime for plugin and classic installer modes. Creates a Python virtual environment, installs requirements, verifies bundled scripts/templates, and explains optional PDF/browser dependencies.
open-chatgpt-in-app-browser
Open ChatGPT in the Codex in-app browser.
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.
playwright-migration
Step-by-step migration guides for moving to Playwright from Cypress or Selenium/WebDriver — command mappings, architecture changes, and incremental adoption strategies.