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/geleynse/gantry/testingnpx skills add geleynse/gantry --skill testinggit clone --depth 1 https://github.com/geleynse/gantryWhat 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.00046 | $0.02441 |
| Opus 5 | $0.00023 | $0.01221 |
| Sonnet 5 | $0.00009 | $0.00488 |
| Haiku 4.5 | $0.00005 | $0.00244 |
Grade A, and why
testing 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing — Gantry Server
All tests use bun:test. No Vitest, no Jest. Tests are co-located with source: foo.ts → foo.test.ts in the same directory (e.g. src/web/routes/accounts.ts / src/web/routes/accounts.test.ts), except a few suite-level integration/smoke tests that live in src/proxy/__tests__/ and src/__tests__/.
Running tests
bun test # full suite (~4200 tests)
bun test src/proxy/__tests__/nudge-state.test.ts # single file
bun test src/web/routes/accounts.test.ts # single file (co-located)
bun run test:coverage # bun test --coverage
The test script in package.json is bun test --max-concurrency=1 — the suite is run serially, not in parallel. CI (.github/workflows/ci.yml) runs plain bun test with continue-on-error: true and the comment "Known cross-file test pollution — all tests pass individually." In practice: if a test fails only when run as part of the full suite (not standalone), suspect shared/global state leaking between files (e.g. a module-level singleton, an un-restored global.fetch, a shared SQLite file) rather than a real bug in your change — re-run the file alone (bun test path/to/file.test.ts) to confirm before chasing it.
Test helper locations
| Path | Provides |
|---|---|
server/src/test/index.ts |
Barrel re-export — import { createMockConfig, createMockSharedState, createMockGameClient, createMockRequest } from "../test/index.js" (or @/test/index.js) |
server/src/test/helpers.ts |
createMockConfig() (valid GantryConfig), createMockSharedState() (valid SharedState — sessions/cache/proxy/fleet), createMockGameClient() (stub GameClient — execute, login, logout, waitForTick, refreshStatus, getCredentials, isConnected), createMockRequest() (minimal Express Request stand-in) |
server/src/test/http-test-server.ts |
startTestServer(app, opts?) / canBindLocalhost() — spins up a real ephemeral-port HTTP server for tests that need one (e.g. WS or raw-socket tests where supertest doesn't apply); retries on bind failure |
server/src/test/setup.ts |
Preloaded before every test (see bunfig.toml below). Registers happy-dom globals, @testing-library/jest-dom matchers, a localStorage mock, mock.restore() + DOM reset in a global beforeEach, and exports MockEventSource (registered as globalThis.EventSource) |
server/src/test/mocks/agents.ts |
createMockAgentStatus(), createMockProxyInfo(), createMockActionProxyStatus(), createMockFleetStatus() — frontend FleetStatus/AgentStatus fixtures |
server/src/test/mocks/game-state.ts |
createMockShipModule(), createMockCargoItem(), createMockShip(), createMockGameState(), createMockFleetGameState() — AgentGameState fixtures (types defined locally to avoid pulling React hooks into server test context) |
server/src/test/mocks/hooks.ts |
createMockAuthState() / createMockViewerAuthState() / createMockLoadingAuthState(), createMockSSEResult(), mockFetchResponse(), mockFetch() — for hook 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 First seen · 157 lines · 46 tokens per session scan A b364f6c53484
testing is a skill published in the GitHub repository geleynse/gantry (3 stars, last pushed 15d ago), licensed MIT. It adds 46 tokens to every session and 2,441 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…