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 commands/ruslan-korneev/claude-plugins/test-fixturegit clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/commands/ruslan-korneev/claude-plugins/test-fixture)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/test-fixture"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/test-fixture.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 | $0.00011 | $0.01399 |
| Opus 5 | $0.00005 | $0.00700 |
| Sonnet 5 | $0.00002 | $0.00280 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
test:fixture 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 4d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /test:fixture
Create a pytest fixture for tests.
Instructions
Step 1: Determine fixture type
- session — AsyncSession for database operations
- client — AsyncClient for API testing
- db — full test database setup
- mock — mock for a dependency
- sample — test data (sample user, sample order, etc.)
Step 2: Determine scope
- function (default) — created for each test
- class — created for each test class
- module — created for each module
- session — created once for the entire test session
Step 3: Determine location
- Shared fixtures →
tests/conftest.py - Module-specific fixtures →
tests/modules/{module}/conftest.py - Local fixtures → in the test file itself
Fixture Templates
AsyncSession with rollback (recommended)
# tests/conftest.py
import pytest
from collections.abc import AsyncGenerator
from sqlalchemy.ext.asyncio import AsyncSession, create_async_engine, async_sessionmaker
from src.core.database import Base
@pytest.fixture(scope="session")
def engine():
"""Test engine — created once."""
return create_async_engine(
"postgresql+asyncpg://test:test@localhost:5432/test_db",
echo=False,
)
@pytest.fixture(scope="session")
async def setup_database(engine):
"""Create tables before tests."""
async with engine.begin() as conn:
await conn.run_sync(Base.metadata.create_all)
yield
async with engine.begin() as conn:
await conn.run_sync(Base.metadata.drop_all)
@pytest.fixture
async def session(
engine,
setup_database,
) -> AsyncGenerator[AsyncSession, None]:
"""Session with automatic rollback after each test."""
async with engine.connect() as connection:
await connection.begin()
session_maker = async_sessionmaker(
bind=connection,
expire_on_commit=False,
)
async with session_maker() as session:
yield session
await connection.rollback()
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.
- 4d ago First seen · 273 lines · 11 tokens per session scan A f01011cac4fe
test:fixture is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 1,399 once invoked, about $0.0001 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 commands, from other repositories
octo-loop
Your first output line MUST be: 🐙 Octopus Loop Mode.
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
sync
Sync the audit manifest with Azure DevOps work items — set the connector up for the first time (connect: verify the transport, report which auth path is in effect, prove access read-only, detect the board's process), push manifest bugs/tasks/phases to ADO (board states, sprint stamp, Remaining Work, comments), pull…
init
Multi-agent codebase audit that GENERATES the audit manifest (phases/tasks) at manifestPath. Interviews you for scope/goals, fans out parallel read-only explorers, synthesizes findings, then presents the proposed phases for approval BEFORE writing — approve to materialize, or park them as proposals for later…
task
Add a tracked task to the audit manifest — every answer is a flag, and the dialogue only covers what the caller did not pass — move one between phases, or cancel work that will not be done. add allocates the id, initializes all orchestrator fields, updates fileIndex, and revalidates; move renumbers a task into another…