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 dayvisonassis/sdd-skills --skill integration-test-writergit clone --depth 1 https://github.com/dayvisonassis/sdd-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/dayvisonassis/sdd-skills/integration-test-writer)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/integration-test-writer"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/integration-test-writer/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/dayvisonassis/sdd-skills/integration-test-writer"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/integration-test-writer.svg" alt="Reviewed on agentmods" width="80" 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.00109 | $0.03163 |
| Opus 5.5 | $0.00044 | $0.01265 |
| Sonnet 5.5 | $0.00022 | $0.00633 |
| Haiku 4.5 | $0.00011 | $0.00316 |
Grade A, and why
integration-test-writer 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 16d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Test Writer
Plan and implement integration tests that validate real behavior against a real test environment: the full request→response lifecycle, and what it changed. Never modifies production code — if a test fails, only the test is adjusted.
The project defines the facts; this skill defines the discipline. All hard rules (project profile, boundary, structure, data, authentication, assertions, query growth, the checklist, execution) are in
references/integration-rules.md— read it before writing. Its first section tells you what to read from the project'sGATES.md: suites, entry point, environment, authentication, data policy, query counter, and the path of the project's own rules, which are binding. The suite's language has its own file,references/languages/<language>.md: the same rules in that language's idiom, its anti-patterns, and a worked query-growth test. Read the one that applies, and only that one (integration-rules.md, "Language"). Background on the SDD flow, not needed to run this skill:https://github.com/dayvisonassis/sdd-skills/blob/main/docs/GUIA_DO_WORKFLOW.md.
Scope: the integration suites the project profile names.
INPUT
target_file_or_endpoint(required) — a handler, a route, or an endpoint (POST /orders).feature(optional) — the feature folder's id (F14); decides where the checklist goes, and which endpoints the query-growth table covers. That folder'sspec.mdandcontract.md, when it has them, are "the spec" the rules refer to.mode(optional) —interactive(default when a user calls) orautonomous(set by implement-feature/evaluator/qa-preflight).language(optional) — the suite's language (javascript,python, …). When given, it wins over what the profile and the repository say.test_file_path(optional) /focus_areas(optional — the behaviors, criteria or values to cover: when given, the run writes only those) /batch_size(optional; default 8, from 5 to 10; a remainder smaller than 5 joins the last batch).evaluation_report(optional) — itskind: testentry selects the mode: an existingtestFile→ correction mode; none → write only what itsmessagenames (a missing query-growth test, or coverage for one rule).
What ships with it
2 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.
- 16d ago Changed · +21 lines fee2f44eef31
- 18d ago Changed · +22 lines · -11 tokens per session 69a647b88040
- 29d ago Changed · +2 lines 69c8c6574d15
- 2mo ago First seen · 92 lines · 120 tokens per session scan A 52018ed735d2
integration-test-writer is a skill published in the GitHub repository dayvisonassis/sdd-skills (3 stars, last pushed 16d ago), licensed MIT. It adds 109 tokens to every session and 3,163 once invoked, about $0.0004 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-31.
Other skills, from other repositories
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
502-frameworks-micronaut-rest
Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via…
api-load-tester
Load tests API endpoints with progressive concurrency. Measures response times, error rates, throughput, and identifies breaking points. Generates a detailed report with latency percentiles, throughput curves, bottleneck analysis, and optimization recommendations.
writing-springboot-tests
Use when writing or adding tests for Spring Boot code at a service's edges: HTTP clients that call other services (WireMock: 4xx and 5xx responses, timeouts, retries), Kafka or RabbitMQ listeners (redelivery, poison messages, dead-letter topics), events published to other services, or full-API tests against real…
add-module
Adds a new application module to this Spring Modulith project with the package layout the ModuleBoundariesTests gate expects, and a module-scoped integration test. Use when the user asks for a new module, bounded context, or feature area that doesn't belong in an existing module.