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/generative-computing/mellea-skills-compiler/readmegit 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/readme)<a href="https://agentmods.dev/commands/generative-computing/mellea-skills-compiler/readme"><img src="https://agentmods.dev/badge/commands/generative-computing/mellea-skills-compiler/readme.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.00000 | $0.00659 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
README 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 — 22 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared Claude Code Commands
Custom slash commands available to all team members working in this repo.
Melleafy v4.3.2
/mellea-fy is a 10-step workflow that converts an agent skill spec (.md) into a fully typed Mellea Python package. The main command orchestrates all steps; sub-commands can be run individually to resume or re-run a specific step.
| Command | File | Step | Description |
|---|---|---|---|
/mellea-fy |
mellea-fy.md |
All | Orchestrator — runs the full 10-step workflow end to end |
/mellea-fy-classify |
mellea-fy-classify.md |
Step 0 | Five-axis classification of the source spec (runtime, modality, archetype, tool disposition, C1–C9) |
/mellea-fy-inventory |
mellea-fy-inventory.md |
Steps 1a + 1b | File inventory and element tagging — produces inventory.json |
/mellea-fy-map |
mellea-fy-map.md |
Step 2 | Element-to-primitive mapping — routes each tagged element to a Mellea primitive and target file |
/mellea-fy-deps |
mellea-fy-deps.md |
Step 2.5 | Dependency audit and elicitation — resolves tool dispositions and produces dependency_plan.json |
/mellea-fy-fixtures |
mellea-fy-fixtures.md |
Step 4 | Fixture generation — produces the fixtures/ subpackage (5–8 test cases) |
/mellea-fy-generate |
mellea-fy-generate.md |
Steps 3 + 5 | Skeleton emission and body generation — produces the populated Python package |
/mellea-fy-artifacts |
mellea-fy-artifacts.md |
Step 6 | Supporting artifact generation — produces mapping_report.md, melleafy.json, SETUP.md, README.md |
/mellea-fy-validate |
mellea-fy-validate.md |
Step 7 | Static validation — 14 formal lint checks; produces intermediate/step_7_report.json |
/mellea-fy-behaviours |
mellea-fy-behaviours.md |
Reference | Known Mellea behaviours and workarounds (KB3–KB9, KB11) — read before generating any code |
/mellea-fy-repair |
mellea-fy-repair.md |
Repair | Inspect a partial or failed run, audit every step's artifacts, and resume the pipeline from the first broken step |
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 · 22 lines · 0 tokens per session scan A 864f38524c79
README is a command published in the GitHub repository generative-computing/mellea-skills-compiler (48 stars, last pushed 9d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 659 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.