What is integration-fixtures-writer?

A test-setup agent that writes pytest fixtures for collecting aggregates and saving them to a database. Pytest is a Python testing tool, and fixtures are reusable test setup functions.

Use it to add aggregate collection and persistence fixtures to an integration test configuration file.

It removes repeated setup code needed by integration tests and avoids adding the same fixtures more than once.

integration-fixtures-writer — Agent for Claude Code by voro6yov

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.

Clone the repo

git clone --depth 1 https://github.com/voro6yov/spec-driven-development

Made for: Claude Code.

Or install persistence-spec, the plugin that ships this one along with the rest of its 2 skills, 23 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/integration-fixtures-writer/github.svg)](https://agentmods.dev/agents/voro6yov/spec-driven-development/integration-fixtures-writer)

Your own site

<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/integration-fixtures-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/integration-fixtures-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/integration-fixtures-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/integration-fixtures-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,976 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 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.

Model	Per session	Once invoked
Fable 5.1	$0.00057	$0.01976
Opus 5.5	$0.00023	$0.00790
Sonnet 5.5	$0.00011	$0.00395
Haiku 4.5	$0.00006	$0.00198

Measured 12d ago against content hash a91dcc9ef69d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

integration-fixtures-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 12d 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.

plugins/persistence-spec/agents/integration-fixtures-writer.md · 140 lines

How it starts

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

You are an integration fixtures writer. Given an aggregate's <domain_diagram> and a project's <tests_dir>, write the collection and persistence fixtures for that aggregate into <tests_dir>/integration/conftest.py:

A test_<plural> collection fixture that bundles every per-state aggregate fixture defined in <tests_dir>/conftest.py.
An add_<plural> persistence fixture that saves each aggregate via unit_of_work and commits.

The agent is idempotent: re-running it for the same aggregate is a no-op; it only emits whichever of the two fixtures is missing. It is also single-aggregate-scoped: it never wires FK dependencies between aggregates.

Pattern docs (umbrella resolution). Resolve <patterns_dir> as the directory containing the persistence-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before composing fixtures, Read <patterns_dir>/collection-fixtures/index.md and <patterns_dir>/persistence-fixtures/index.md in full — they are the authoritative formatters for the templates. If either folder is missing, abort with Error: pattern '<name>' has no folder under the persistence-spec:patterns umbrella at <patterns_dir>. Load no other pattern docs.

Arguments

<domain_diagram> (first argument): absolute path to the aggregate's domain Mermaid diagram (<dir>/<stem>.md).
<tests_dir> (second argument): absolute path to the project's tests directory (as resolved by @spec-core:target-locations-finder); must contain conftest.py and integration/conftest.py.

Path resolution. Derive the persistence command-repo spec file from <domain_diagram> per spec-core:naming-conventions: <command_spec_file> = <dir>/<stem>.persistence/command-repo-spec.md, where <dir> and <stem> are recovered from <domain_diagram> per the recovery table in that skill.

Workflow

Step 1 — Verify target conftests exist

[ -f "<tests_dir>/conftest.py" ] && echo ROOT_OK || echo ROOT_MISSING
[ -f "<tests_dir>/integration/conftest.py" ] && echo INT_OK || echo INT_MISSING

Read the full file on GitHub · 140 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.

12d ago First seen · 140 lines · 57 tokens per session scan A a91dcc9ef69d

Subscribe to this mod's changes

integration-fixtures-writer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,976 once invoked, about $0.0002 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-10-04.

Databases Testing

verifier

Use this agent when verifying that implementation meets success criteria, validating phase completion, checking plan coverage before execution, or performing pre-ship validation. Examples: Context: A phase has been fully built and reviewed, and needs final verification before moving on. user: "Verify that the database…

lgbarn/shipyard · 278 tokens

vibe-seed-check-worker

Checks symphony-alpha's vibe seed against fresh main for the vibe-seed-refresh orchestrator. Refreshes a dedicated detached check worktree, runs pnpm vibe check and reads the latest Vibe Seed Walk run on main, and returns CLEAN or DRIFT with a short drift list. Changes no tracked files.

closedloop-ai/claude-plugins · 69 tokens

integration-fixtures-writer

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Arguments

Workflow

Step 1 — Verify target conftests exist

What this file has done since we first saw it

Other agents, from other repositories

verifier

vibe-seed-check-worker

test_case_verifier

business_logic

edge_cases

seed-generator