mellea-skills-compiler: Command for Claude Code

.claude/commands/mellea-fy-fixtures.md

mellea-fy-fixtures is a command for Claude Code from generative-computing/mellea-skills-compiler. It costs 0 tokens per session (1,961 once invoked), scanned A, original, Apache-2.0.

A command that creates test fixtures for a generated Python package. Fixtures are sample inputs and expected cases used to check that the package works.

In plain words
What is it for?
Generating 5–8 test cases across at least three categories, then running them with pytest.
Why use it?
It creates runtime tests in a consistent place, helping catch problems that code-style checks cannot detect.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is generative-computing/mellea-skills-compiler's own configuration. It tells Claude Code how to work on mellea-skills-compiler itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mellea-skills-compiler configures →

Reuse

Borrowing it

Nothing to install: this file belongs to generative-computing/mellea-skills-compiler. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/generative-computing/mellea-skills-compiler/main/.claude/commands/mellea-fy-fixtures.md
Clone the repo
git clone --depth 1 https://github.com/generative-computing/mellea-skills-compiler

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 mellea-fy-fixtures

README.md
[![agentmods](https://agentmods.dev/badge/commands/generative-computing/mellea-skills-compiler/mellea-fy-fixtures/github.svg)](https://agentmods.dev/commands/generative-computing/mellea-skills-compiler/mellea-fy-fixtures)
Your own site
<a href="https://agentmods.dev/commands/generative-computing/mellea-skills-compiler/mellea-fy-fixtures"><img src="https://agentmods.dev/badge/commands/generative-computing/mellea-skills-compiler/mellea-fy-fixtures/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.

agentmods 80×15 button for mellea-fy-fixtures

Your own site · 80×15
<a href="https://agentmods.dev/commands/generative-computing/mellea-skills-compiler/mellea-fy-fixtures"><img src="https://agentmods.dev/badge/commands/generative-computing/mellea-skills-compiler/mellea-fy-fixtures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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,961 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01961
Opus 5 $0.00000 $0.00981
Sonnet 5 $0.00000 $0.00392
Haiku 4.5 $0.00000 $0.00196

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

Security

Grade A, and why

mellea-fy-fixtures 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.

.claude/commands/mellea-fy-fixtures.md · 176 lines

How it starts

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

Melleafy Step 4: Fixture Generation

Version: 4.1.1 | Prereq: Step 3 complete (skeleton emitted with finalised run_pipeline signature) | Produces: <package_name>/fixtures/

Output path rule (Rule OUT-4): fixtures/ is written inside <package_name>/ — NOT at the skill root. It is test-only and intentionally excluded from the installed package by pyproject.toml's [tool.setuptools.packages.find]. Run fixtures via python -m pytest <package_name>/fixtures/ from the skill root.

Step 4 generates 5–8 test fixtures covering ≥3 C-categories. Fixtures are the primary means by which the generated package can be validated at runtime (Step 7's lints are static-only).

Rule 4-1 — Batched fixture generation as JSON: Generate all fixture specifications in a single LLM invocation. The invocation receives the run_pipeline signature, the element mapping summary, and the C-category coverage requirement, and returns one JSON object conforming to .claude/schemas/fixtures_emission.schema.json — not Python source. The deterministic writer at .claude/melleafy/writers/fixtures_writer.py renders the per-fixture .py files plus fixtures/__init__.py from that JSON. The model never writes Python source for fixtures directly. This makes shape drift (pytest-style tests, INPUT-only modules, hand-rolled __init__.py exports) structurally unreachable — every legal JSON instance produces a contract-correct fixture package.


CRITICAL: Input parameter matching

The keys in every fixture's inputs object MUST be identical to the parameter names of the run_pipeline function in pipeline.py. This is not optional. A fixture with {"text": "..."} for a pipeline that expects run_pipeline(user_query=...) will fail at runtime with a TypeError. Before emitting JSON, verify the exact parameter names from the generated pipeline function. The schema cannot enforce this — it's the model's responsibility to match.


Fixture structure

Read the full file on GitHub · 176 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. 12d ago First seen · 176 lines · 0 tokens per session scan A 0ce8b00954ec

Subscribe to this mod's changes

mellea-fy-fixtures is a command published in the GitHub repository generative-computing/mellea-skills-compiler (50 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,961 tokens. 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-30.