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-dengit 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-den)<a href="https://agentmods.dev/skills/danilods/matilha-skills/matilha-den"><img src="https://agentmods.dev/badge/skills/danilods/matilha-skills/matilha-den/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-den"><img src="https://agentmods.dev/badge/skills/danilods/matilha-skills/matilha-den.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.00031 | $0.00495 |
| Opus 5 | $0.00015 | $0.00247 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
matilha-den 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 11d 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.
What it actually says
When this fires
Project or milestone completion. User wants to distill what was learned, what patterns emerged, what to reuse. Writes docs/matilha/den/<date>-<topic>.md.
Preconditions
project-status.mdexists.- At least one wave completed.
Execution Workflow
- Read completed waves from project-status.md via Read tool.
- Prompt user for topic (e.g., "auth system patterns").
- Read relevant wave outputs (commits via Bash, spec/plan/review_report via Read) for the topic.
- Synthesize via Write into
docs/matilha/den/<date>-<topic>.mdwith sections: context, patterns observed, decisions + why, would-do-differently. - Update project-status.md
recent_decisionswith pointer to the den file.
Rules: Do
- Cite specific commits + files in findings.
- Include "would-do-differently" section (honest retrospective).
- Timestamp the filename.
Rules: Don't
- Delete existing den files (keep history).
- Write generic advice (be specific to THIS project).
Expected Behavior
Knowledge captured in navigable markdown that informs future /matilha-pack packaging.
Quality Gates
- Den file exists at
docs/matilha/den/<date>-<topic>.md. - Cited commits are real (verifiable via git log).
Companion Integration
No companion integrations in Wave 4a.
Output Artifacts
docs/matilha/den/<date>-<topic>.md.
Example Constraint Language
- Use "must" for: cite wave(s) being distilled.
- Use "should" for: include would-do-differently.
- Use "may" for: split across multiple files for a large project.
Troubleshooting
- "no waves completed": Run
/matilha-gatherfirst. - "topic too broad": Split into multiple den files per sub-topic.
CLI shortcut (optional)
matilha den <topic>(future CLI command; not shipped yet).
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.
- 11d ago First seen · 68 lines · 31 tokens per session scan A cfe2f4e0166b
matilha-den is a skill published in the GitHub repository danilods/matilha-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 495 once invoked, about $0.0002 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
init
Opt-in onboarding for the mARC agent team. Scaffolds a per-repo team binding so the team graduates from ephemeral session-memory to persistent, versioned config — without ever writing a file silently. Discovers the repo's org/repo/ project at runtime via gh, prefills {{ agentsdir }}/team.toml, and (optionally) a lean…
knowledge-wiki
A tool that turns useful lessons from coding sessions into general articles for a team wiki. A wiki is a collection of linked reference pages, and this one can be kept locally or shared through a Git repository.
dream
Prunes and consolidates the project's auto-memory to keep it minimal — deletes stale, wrong, or redundant memories, merges overlapping ones into existing files, and trims the index. Strong bias against growth: never creates new memory files and never stores new facts. Verifies staleness against the current codebase…
optimize-learnings
Audit and curate the learnings memory namespace — the one namespace nothing re-derives, so the only one that rots. Runs moflo's mechanical audit to nominate stale, unused, and near-duplicate entries, then decides entry by entry whether to keep, retire, compress, or merge, and propagates the result to the shared…
memory-team
Guided setup for sharing moflo's durable learnings through a git-tracked JSONL artifact — for a whole TEAM on one repo, OR for one person across several MACHINES (a team of one). Use when the user says "share learnings with my team", "commit our moflo memory", "sync memory across my laptop and desktop", "set up…
magic-compact
Compact this Claude Code session.