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.
curl -O https://raw.githubusercontent.com/generative-computing/mellea-skills-compiler/main/.claude/commands/mellea-fy.mdgit clone --depth 1 https://github.com/generative-computing/mellea-skills-compilerWrote 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/generative-computing/mellea-skills-compiler/mellea-fy)<a href="https://agentmods.dev/commands/generative-computing/mellea-skills-compiler/mellea-fy"><img src="https://agentmods.dev/badge/commands/generative-computing/mellea-skills-compiler/mellea-fy.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.1 | $0.00000 | $0.03597 |
| Opus 5 | $0.00000 | $0.01799 |
| Sonnet 5 | $0.00000 | $0.00719 |
| Haiku 4.5 | $0.00000 | $0.00360 |
Grade A, and why
mellea-fy 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 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.
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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Melleafy: Decompose an Agent Spec into Mellea Code
Spec version: 4.3.2 (2026-04-28) — 10-step workflow with source-runtime detection, dependency audit, API reference grounding, and 14 formal lints with repair loop.
You are a Mellea decomposition specialist. Given a path to an agent .md file, produce an executable Python package using the Mellea generative programming library. This orchestrator file describes the overall workflow; step-specific guidance lives in the sub-commands listed below.
Your input: $ARGUMENTS — path to an agent .md file (or workspace directory for multi-file source runtimes).
Your output: A generated Python package plus intermediate artifacts and a mapping report.
The 10-step workflow
Run these steps in order. Each step has a dedicated sub-command with the full specification.
[source spec on disk]
│
▼
Step 0: Classify the spec along five axes
│ → classification.json
│ Sub-command: /mellea-fy-classify
▼
Steps 1a + 1b: Inventory files → tag elements + assign C1-C9 categories
│ Step 1b Pass 1 (multi-file): [per-file section discovery — ║ parallel ║]
│ → inventory.json
│ Sub-command: /mellea-fy-inventory
▼
Step 2: Map elements to Mellea primitives
│ Judgment calls: [all independent elements — ║ parallel ║]
│ → element_mapping.json (TOOL_TEMPLATE entries provisional)
│ Sub-command: /mellea-fy-map
▼
Step 2.5: Dependency audit + elicitation → commit dispositions + API reference
│ → dependency_plan.json, element_mapping_amendments.json, mellea_api_ref.json
│ Sub-command: /mellea-fy-deps ← NEW in v4.0 — do not skip
▼
Step 3: Emit skeleton files
│ → empty Python files with structure (run_pipeline signature locked here)
│
Step 4: Generate fixtures
│ → fixtures/ subpackage (5-8 fixtures, ≥3 C-categories)
│ Sub-command: /mellea-fy-fixtures
│ (uses Step 3 skeleton's run_pipeline signature as grounding source)
▼
Step 5: Generate per-element code bodies (3-phase structure)
│ Phase A: [schemas.py, config.py, requirements.py, slots.py, tools.py/constrained_slots.py, mobjects.py, loader.py — ║ parallel ║]
│ Phase B: pipeline.py (after Phase A)
│ Phase C: main.py (after Phase B)
│ → populated Python files (fixtures/ available as grounding context)
│ Sub-command: /mellea-fy-generate (covers Steps 3 + 5)
▼
Step 6: Emit supporting artifacts
│ Narrative batching: [classification_narrative + deferred_feature_entry + judgment_call_explanation (≤3) — ║ parallel ║ where applicable]
│ → mapping_report.md, melleafy.json, SETUP.md, README.md
│ → SKILL.md (non-.md sources only — CLI compatibility shim, WIP)
│ Sub-command: /mellea-fy-artifacts
▼
Step 7: Static validation (14 formal lints)
│ Tier 1: [all .py files — ast.parse() ║ parallel ║, then import check]
│ Tier 2: [all 13 lints — ║ parallel ║]
│ → step_7_report.json
│ Sub-command: /mellea-fy-validate
│
├── [PASS] ──────────────────────────────────────────────────────────────►
│ ▼
└── [FAIL — Tier 1 or structural Tier 2, repair_round < 2] [generated package on disk]
│
▼
Re-invoke /mellea-fy-generate (repair mode, failing files only)
│ → re-run Step 7, increment repair_round
│
└── [FAIL — repair_round = 2, OR session-boundary / category-specific]
→ halt, preserve .melleafy-partial/
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.
- 8d ago First seen · 224 lines · 0 tokens per session scan A 865944fa18d7
mellea-fy is a command published in the GitHub repository generative-computing/mellea-skills-compiler (48 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,597 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.
Other commands, from other repositories
type-coverage
Vérification Couverture des Types Python.
execute-pydantic-ai-prp
Implement a Pydantic AI agent using the PRP file.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
scaffold-service
Scaffold a thin ArchiPy FastAPI or gRPC service under services/{domain}/v{n}/.
savant-python
Python performance optimization with Python Developer agent.
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.