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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/arch-health)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/arch-health"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/arch-health/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/commands/gonzalezpazmonica/pm-workspace/arch-health"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/arch-health.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.00016 | $0.00784 |
| Opus 5 | $0.00008 | $0.00392 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
arch-health 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 9d 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.
This is a copy
100% identical to arch-health — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/arch-health
🦉 Savia mide la salud de tu arquitectura con métricas objetivas.
Cargar perfil de usuario
Grupo: Architecture & Debt — cargar:
identity.md— nombre, rolprojects.md— proyecto targetpreferences.md— detail_level
Subcomandos
/arch-health— informe completo de salud arquitectónica/arch-health --drift— solo detección de drift/arch-health --coupling— solo métricas de acoplamiento
Flujo
Paso 1 — Ejecutar fitness functions
Ejecutar las reglas definidas por /arch-fitness (si existen):
| Fitness Function | Qué mide |
|---|---|
| Layer independence | ¿Las capas respetan sus dependencias? |
| No circular deps | ¿Hay dependencias circulares? |
| Naming conventions | ¿Los nombres siguen las convenciones? |
| File size limits | ¿Hay ficheros excesivamente grandes? |
| Import limits | ¿Hay ficheros con demasiados imports? |
Paso 2 — Detectar drift arquitectónico
Comparar estado actual vs. ADRs activos:
- ¿Se están respetando las decisiones documentadas?
- ¿Hay nuevos patrones no documentados emergiendo?
- ¿Hay violaciones de las convenciones del lenguaje?
Paso 3 — Calcular métricas de acoplamiento
| Métrica | Cálculo |
|---|---|
| Afferent Coupling (Ca) | Módulos que dependen de este |
| Efferent Coupling (Ce) | Módulos de los que este depende |
| Instability | Ce / (Ca + Ce) — 0=estable, 1=inestable |
| Abstractness | Interfaces / Total clases |
| Distance | |A + I - 1| — 0=zona óptima |
Paso 4 — Generar informe
🦉 Architecture Health — {proyecto}
📊 Health Score: {N}/100 {🟢|🟡|🔴}
✅ Fitness Functions: {passed}/{total} PASS
🟢 Layer independence — PASS
🔴 No circular deps — FAIL (A→B→C→A)
🟢 Naming conventions — PASS
🔄 Drift Detection:
⚠️ ADR-003 (Use Repository Pattern): 2 violaciones
✅ ADR-005 (CQRS): Respetado
📐 Coupling:
Top acoplados: {módulo} (Ce=12), {módulo} (Ce=9)
Inestables: {módulo} (I=0.9), {módulo} (I=0.8)
💡 Recomendaciones:
1. Romper dependencia circular A→B→C→A
2. Reducir coupling de {módulo} extrayendo interfaz
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.
- 9d ago First seen · 113 lines · 16 tokens per session scan A 4fbb98f2f9e0
arch-health is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 784 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to arch-health, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.