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 skills add danilods/matilha-skills --skill matilha-composegit clone --depth 1 https://github.com/danilods/matilha-skillsWrote 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/skills/danilods/matilha-skills/matilha-compose)<a href="https://agentmods.dev/skills/danilods/matilha-skills/matilha-compose"><img src="https://agentmods.dev/badge/skills/danilods/matilha-skills/matilha-compose/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.
<a href="https://agentmods.dev/skills/danilods/matilha-skills/matilha-compose"><img src="https://agentmods.dev/badge/skills/danilods/matilha-skills/matilha-compose.svg" alt="Reviewed on agentmods" width="80" 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.00148 | $0.06604 |
| Opus 5 | $0.00074 | $0.03302 |
| Sonnet 5 | $0.00030 | $0.01321 |
| Haiku 4.5 | $0.00015 | $0.00660 |
Grade A, and why
matilha-compose 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 10d 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this fires
Fires BEFORE any creative-work or software-construction skill (including superpowers:brainstorming, superpowers:writing-plans) when BOTH conditions hold:
-
Matilha is installed — this skill (
matilha:matilha-compose) is visible in the ambient skill list. This is implicit: if you are reading this body, matilha is loaded for the current workspace. -
Software-construction intent — the user prompt signals any of:
- Planning / spec authoring ("plan this", "write a spec", "lay out phases")
- Designing / UX / UI ("how should this look", "which UI", "what component")
- Researching / discovery ("what are the options for...", "investigate...")
- Building / implementing ("I'm building...", "adding...", "construindo...")
- Reviewing / quality ("review this PR", "check this code")
- Dispatching waves / parallel work ("split this into SPs", "dispatch waves")
- Status / next action ("where am I?", "what's next?")
- General creative exploration ("I'm thinking about...", "exploring...")
Project-context signals (docs/matilha/ directory, project-status.md file, any matilha-*-pack skill visible) are supplementary context for routing decisions, not activation gates. Matilha methodology applies broadly whenever the plugin is installed — these signals only shift how compose dispatches (to which specific matilha phase skill vs. superpowers skill).
Positive examples (compose fires):
- "Estou construindo MVP de 4 semanas... Como estruturo os agents?" → general creative → brainstorming with pack preamble (harness-pack if visible)
- "Quero planejar a feature de export CSV" → planning intent → matilha-plan (may lazy-bootstrap docs/matilha/)
- "What's the current phase?" → status intent → matilha-howl
- "Review my code changes" → quality intent → superpowers:brainstorming or matilha-review depending on what matilha finds
Negative examples (compose does NOT fire):
- Compose is NOT installed (different workspace) → this skill is absent from ambient list
- Prompt is pure factual / non-construction ("what's the capital of France?") → no software-construction signal
- User invokes a specific skill directly via slash command (e.g.,
/matilha-howl) → direct invocation bypasses compose
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 372 lines · 148 tokens per session scan A f58abab8909b
matilha-compose is a skill published in the GitHub repository danilods/matilha-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 148 tokens to every session and 6,604 once invoked, about $0.0007 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 skills, from other repositories
skill-dev
Use this skill when creating or refining Claude Code skill definitions. Skills are model-invoked capabilities that Claude activates autonomously based on context. Helps design focused skills with discovery-optimized descriptions, proper directory structures, and supporting resources. Automatically invoked when user…
plugin-dev
Use this skill when creating or refining Claude Code plugins. Plugins are bundled collections of agents, skills, commands, hooks, and MCP servers that provide cohesive functionality. Helps design proper directory structures, plugin.json configuration, marketplace distribution, and installation workflows. Automatically…
agent-dev
Use this skill when creating or refining Claude Code sub-agent definitions. Helps design specialized AI assistants with proper YAML frontmatter, system prompts, tool access, and example-driven descriptions. Automatically invoked when user requests "create an agent", "design a sub-agent", "make a specialist", or…
command-dev
Use this skill when creating or refining custom Claude Code slash commands. Slash commands are user-invoked reusable prompts that can accept arguments, reference files, and execute bash operations. Helps design command syntax, argument handling, file references, bash execution, and frontmatter configuration.…
mcp-server-dev
Create MCP servers — multi-tool services exposed via Model Context Protocol. Use this skill whenever users mention MCP servers, building servers, server scaffolding, tool registration, or want to package tools for distribution via uvx or npx. Also use when the conversation involves stdio transport, server lifecycle…
mcp-tool-dev
Create MCP tools — individual tool functions exposed via Model Context Protocol. Use this skill whenever users mention MCP tools, tool handlers, tool functions, tool definitions, or want to add capabilities to an MCP server. Also use when the conversation involves designing tool schemas, writing tool descriptions, or…