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 GalaxyRuler/Galactic-skills --skill test-backendgit clone --depth 1 https://github.com/GalaxyRuler/Galactic-skillsWrote 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/galaxyruler/galactic-skills/test-backend)<a href="https://agentmods.dev/skills/galaxyruler/galactic-skills/test-backend"><img src="https://agentmods.dev/badge/skills/galaxyruler/galactic-skills/test-backend.svg" alt="Measured on agentmods" height="20"></a>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.00140 | $0.01052 |
| Opus 5 | $0.00070 | $0.00526 |
| Sonnet 5 | $0.00028 | $0.00210 |
| Haiku 4.5 | $0.00014 | $0.00105 |
Grade A, and why
test-backend 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test-backend — portable back-end testing runner
Execute the Back-end Testing Playbook (playbook.md, same folder) against the current service and emit a findings report. Read it first. Works for any backend; a project-level test-backend overrides this when present.
Scope: an argument narrows to an endpoint/service (/test-backend /api/orders). No argument = the endpoint map from Phase 0.
Phase 0 — Detect the stack (do this first)
Read manifests + config and pick commands. Detect:
- Language/framework: Node (Express/Fastify/Nest), Python (FastAPI/Django/Flask), Go, Java/Kotlin (Spring), Ruby (Rails), .NET, etc.
- Test runner: vitest/jest · pytest · go test · JUnit · rspec · xunit.
- DB/ORM + cache/queue: Prisma/TypeORM/Sequelize · SQLAlchemy/Django ORM · GORM · Hibernate; Redis/Postgres/Kafka.
- Spec: OpenAPI/Swagger · GraphQL SDL · protobuf — the contract source of truth.
- Containers/load/DAST: docker-compose / Testcontainers present? k6/JMeter/Gatling/Locust? OWASP ZAP?
Map to: lint, unit, integration, "start test deps", seed, load. If a tool is absent, degrade that phase to a manual checklist + one-line setup note — never fail the run, never silently pass it.
Read a project
TESTING.md/docs/testing/*/ the Project appendix inplaybook.mdand prefer its commands + auth model.
Runbook (phase-gated — see playbook.md for the why)
- Scope & map — endpoints × method × auth-context; deps; invariants; SLOs + critical journeys.
- Static base — type-check/lint; schema = contract source of truth.
- Unit — pure logic; independent golden master for critical math.
- Integration (widest) — real DB/cache via Testcontainers/compose; in-process route injection; happy/validation/not-found/auth boundary; DB effects, seed determinism, cache + fallback.
- Contract — request+response schema for every endpoint + every declared status code; spec-driven provider tests (Schemathesis/Dredd); consumer-driven (Pact) across services; breaking-change diff vs the committed spec.
- Data & invariants — golden-master parity; deterministic IDs; ETL/sync idempotency + partial-failure isolation; migration safety.
- Resilience & chaos — kill/slow/garble each dep; assert graceful degradation, error-shape, timeouts, retry/backoff, rate-limit; combine Load+Chaos where possible.
- Security — OWASP API Top 10 2023 — BOLA two-account test (A can't touch B's objects) + BOPLA/BFLA; injection (parameterized + schema, fuzz); SSRF on user-influenced fetches; resource caps + rate-limit (+
trustProxy); headers/CORS/no-leak; upstream-data sanitization. Optional ZAP DAST (passive first, non-prod, seed with the spec). - Performance & SLO — encode SLOs as load-tool thresholds (p95/p99, error rate); ramp-up→steady→ramp-down on critical journeys; cache + pool behavior under load. If no load tool → emit scenario + threshold table.
- Report —
docs/testing/reports/<date>-backend.md(or./backend-test-report-<date>.md); map security findings to OWASP API IDs; perf vs SLO; contract diffs explicit.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed f423b3968fd7
- 8d ago First seen · 40 lines · 140 tokens per session scan A f5776131bfb1
test-backend is a skill published in the GitHub repository GalaxyRuler/Galactic-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 140 tokens to every session and 1,052 once invoked, about $0.0007 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
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
prowler-test-api
Testing patterns for Prowler API: JSON:API, Celery tasks, RLS isolation, RBAC. Trigger: When writing tests for api/ (JSON:API requests/assertions, cross-tenant isolation, RBAC, Celery tasks, viewsets/serializers).
python-sdk
Implement or modify Python SDK behavior under python/composio, including tools, toolkits, sessions, auth configs, connected accounts, client integration, and shared Python models. Use for Python core runtime/API work; pair with python-testing and cross-sdk-parity when TypeScript must match.
convex-test
Generate convex-test tests for the app's Convex functions.
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.