backend-testing

backend-testing is a skill for Claude Code from ironbee-ai/ironbee-devtools-skills. It costs 74 tokens per session (3,141 once invoked), scanned B, original, MIT.

A guide for testing a backend service from end to end, meaning it checks the real service, its logs, and its database together. It covers HTTP, gRPC, GraphQL, and WebSocket connections.

In plain words
What is it for?
Use it to send test requests, replay curl or HAR requests, inspect file, Docker, or Kubernetes logs, verify database changes, and create or undo test data.
Why use it?
A successful response alone may not prove that the server logged the right event or changed the right database records. This connects those checks through one trace ID, a label shared across related requests and logs.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to send test requests, replay curl or HAR requests, inspect file, Docker, or Kubernetes logs, verify database changes, and create or undo test data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ironbee-ai/ironbee-devtools-skills/backend-testing
Install

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.

Any agent
npx skills add ironbee-ai/ironbee-devtools-skills --skill backend-testing
Clone the repo
git clone --depth 1 https://github.com/ironbee-ai/ironbee-devtools-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for backend-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/ironbee-ai/ironbee-devtools-skills/backend-testing.svg)](https://agentmods.dev/skills/ironbee-ai/ironbee-devtools-skills/backend-testing)
Your own site
<a href="https://agentmods.dev/skills/ironbee-ai/ironbee-devtools-skills/backend-testing"><img src="https://agentmods.dev/badge/skills/ironbee-ai/ironbee-devtools-skills/backend-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,141 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00074 $0.03141
Opus 5 $0.00037 $0.01571
Sonnet 5 $0.00015 $0.00628
Haiku 4.5 $0.00007 $0.00314

Measured 8d ago against content hash c57df6db02bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

backend-testing scanned grade B with 2 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 8d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

--source '{"kind":"curl","value":"curl -X POST https://api.example.com/orders -d ..."}' \

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

description: Test backend services end-to-end. Use when the user wants to drive HTTP/gRPC/GraphQL/WebSocket endpoints against a real server, correlate requests with server logs (file/Docker/Kubernetes), verify database s
skills/backend-testing/SKILL.md · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Backend Testing Skill

End-to-end backend verification with the IronBee Backend DevTools CLI. Drive requests, watch logs, and assert on database state — all in one session.

See the full CLI reference at ironbee-backend-devtools-cli. Domain-level docs: request, log, db, o11y.

When to Use

This skill activates when:

  • User wants to test backend APIs over HTTP/1.1, HTTP/2, gRPC, GraphQL, or WebSocket
  • User needs to assert on log lines that a request produced (file, Docker, or Kubernetes logs)
  • User needs to verify that a request changed exactly the right database rows
  • User wants to replay a captured curl command or HAR entry
  • User needs to seed test fixtures and roll them back automatically
  • User wants to correlate a request chain with a single W3C trace id

Core principle: correlate by trace id

Pin a trace id once on the session and every request automatically carries it. Then read your server logs filtered by that trace id — that's the cleanest agent-driven verification loop.

SESSION="--session-id e2e"
TRACE=$(ironbee-backend-devtools-cli $SESSION --json o11y new-trace-id | jq -r .traceId)
ironbee-backend-devtools-cli $SESSION request http --url "https://api.example.com/orders" --method POST --body '{"kind":"json","value":{"sku":"ABC"}}'
ironbee-backend-devtools-cli $SESSION --json log read --source app --pattern "$TRACE" --parse-json --select '["timestamp","level","msg","span_id"]'

# Same id, read back as spans from the IronBee platform (needs SERVICE_OAUTH_TOKEN or SERVICE_API_KEY)
ironbee-backend-devtools-cli $SESSION --json o11y get-trace --wait-ms 10000 --status error

Capabilities

HTTP / GraphQL / gRPC / WebSocket requests

# HTTP with JSON body
ironbee-backend-devtools-cli --json request http \
  --url "https://api.example.com/orders" \
  --method POST \
  --body '{"kind":"json","value":{"sku":"ABC","qty":2}}'

# GraphQL
ironbee-backend-devtools-cli --json request graphql \
  --url "https://api.example.com/graphql" \
  --query 'mutation($s:String!){createOrder(sku:$s){id}}' \
  --variables '{"s":"ABC"}'

# gRPC unary via .proto file
ironbee-backend-devtools-cli --json request grpc \
  --target "api.example.com:443" \
  --service "orders.v1.OrderService" \
  --method "GetOrder" \
  --proto-source '{"kind":"protoFile","path":"./protos/orders.proto"}' \
  --request '{"orderId":"abc-123"}'

# WebSocket — multi-step (open / send / receive / close)
CONN=$(ironbee-backend-devtools-cli --json request websocket-open --url "wss://api.example.com/stream" | jq -r .connectionId)
ironbee-backend-devtools-cli request websocket-send --connection-id "$CONN" --data '{"kind":"json","value":{"subscribe":"orders"}}'
ironbee-backend-devtools-cli --json request websocket-receive --connection-id "$CONN" --max-count 50 --timeout-ms 5000
ironbee-backend-devtools-cli request websocket-close --connection-id "$CONN"

Read the full file on GitHub · 236 lines

Changes

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.

  1. 8d ago First seen · 236 lines · 74 tokens per session scan B c57df6db02bc

Subscribe to this mod's changes

backend-testing is a skill published in the GitHub repository ironbee-ai/ironbee-devtools-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 3,141 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

backend/testing-guide

A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.

echoVic/boss-skill · 30 tokens

Author and Run Regression Tests with Agent QA

Use Agent QA's CLI and MCP server to author, validate, run, debug, and triage natural-language web and mobile regression tests with persistent test memory and reviewable run evidence.

agentskillexchange/skills · 46 tokens

devlab-integration-fullstack

A guide to testing complete business flows across a frontend, backend services, databases, and other connected systems. It uses tools such as Playwright, Jest, SuperTest, Testcontainers, and mock servers to test multi-service setups.

seed-forge/harness-ai-kit · 42 tokens

audit-realworld

Read-only full-stack conformance audit against RealWorld ("Conduit"): formal API spec, shared E2E suite, and closest-stack reference. Use when "audit against RealWorld", "Conduit conformance", or "is my full-stack app complete?". General user journeys → audit-ux-journeys.

kensaurus/cursor-kenji · 67 tokens

nestjs-testing-expert

NestJS testing mechanics with Jest — building testing modules, mocking providers and repositories, writing service and controller specs, and driving HTTP end-to-end tests through the real application. Use for any test touching a NestJS service, controller, guard, module, or API endpoint, including test-module setup…

shipshitdev/skills · 77 tokens

Express.js Testing Patterns

Express.js API testing with supertest, middleware testing, route handler testing, error handling verification, and authentication testing.

PramodDutta/qaskills · 28 tokens