Borrowing it
Nothing to install: this file belongs to dbareagimeno/enu. 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/dbareagimeno/enu/develop/.claude/skills/salud/SKILL.mdgit clone --depth 1 https://github.com/dbareagimeno/enuWrote 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/dbareagimeno/enu/salud)<a href="https://agentmods.dev/skills/dbareagimeno/enu/salud"><img src="https://agentmods.dev/badge/skills/dbareagimeno/enu/salud/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/dbareagimeno/enu/salud"><img src="https://agentmods.dev/badge/skills/dbareagimeno/enu/salud.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.00100 | $0.01249 |
| Opus 5 | $0.00050 | $0.00624 |
| Sonnet 5 | $0.00020 | $0.00250 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
salud 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pasada de salud (capa mecánica)
Cuatro detectores mecánicos: reproducibles, sin falsos positivos de LLM, y
cada uno caza una familia de fallos que las verificaciones habituales (CI por
push, DoD por sesión, juicio por diff) no cubren. El principio: el
calendario solo es buen trigger para lo que cambia aunque el código no cambie
(el corpus de fuzzing crece, las CVEs se publican, los interleavings son
loterías); para lo demás el trigger es el cambio (eso ya lo hacen CI y
/juicio).
Ejecuta los cuatro pasos; los largos, en paralelo/segundo plano. Presupuesto orientativo total: 30-45 min de máquina, casi todo desatendido.
1 · Fuzzing (dianas en internal/runtime/fuzz_test.go)
Seis dianas con invariantes fuertes sobre la lógica 🔒: FuzzSSEChunkSplit
(S20, equivalencia bajo partición de chunks), FuzzDecodeInputChunkSplit
(CP-7, disciplina pending/flush del driver), FuzzComputeDiffReconstruct
(S25, aplicar los hunks reconstruye b), FuzzWrapText y FuzzTruncateText
(S22, anchura acotada + contenido conservado), FuzzMarkdownStreamingSafe
(S23, prefijos arbitrarios no rompen).
for t in FuzzSSEChunkSplit FuzzDecodeInputChunkSplit FuzzComputeDiffReconstruct \
FuzzWrapText FuzzTruncateText FuzzMarkdownStreamingSafe; do
go test ./internal/runtime/ -run "^$t$" -fuzz "^$t$" -fuzztime 3m
done
- El corpus vive en
$GOCACHE/fuzzy se acumula entre pasadas: cada ejecución parte de donde llegó la anterior — el tiempo invertido se compone. - Un fallo deja un caso mínimo en
internal/runtime/testdata/fuzz/<diana>/: commitéalo (se convierte en test de regresión permanente que CI ejecuta como semilla) y trata el fallo como hallazgo: ¿bug de código (→ arreglar citando la diana) o invariante mal formulado en la diana (→ corregir la diana explicando por qué)? - Si una sesión nueva añade lógica 🔒 parseadora o con bordes, añade su diana aquí; el inventario de dianas crece como el 🔒: nunca se relaja.
- CI solo ejecuta las semillas (un
go testnormal no fuzzea): el coste del fuzzing vive en esta skill, no en cada push.
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 · 92 lines · 100 tokens per session scan A d061bee1ab6a
salud is a skill published in the GitHub repository dbareagimeno/enu (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 100 tokens to every session and 1,249 once invoked, about $0.0005 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
colony-dogfood
Conduz um experimento de dogfood onde a colônia Pi executa uma task do .project/tasks.json em dois tempos (research → código) com gates do operador. Use quando o operador quiser ativar um experimento colony-experiment-phase1 ou colony-experiment-phase2.
create-pi-web-extension
Como criar/extender extensões web no pi com arquitetura determinística, segurança mínima e testes automatizados (smoke + e2e via pi-test-harness).
test-pi-extension
Como testar extensões pi com @marcfargas/pi-test-harness. Use quando o usuário quiser testar uma extensão, criar testes automatizados, ou validar que um pacote pi funciona após publish.
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
codex-claude-worker
Translate natural-language user requests into bounded Claude Code worker tasks while Codex or ChatGPT remains the supervisor. Use when the user gives an ordinary prompt and wants Codex to clarify scope, choose a safe work boundary, generate a worker prompt, approve or defer worker execution, read run summaries and…