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-fitness)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/arch-fitness"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/arch-fitness/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-fitness"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/arch-fitness.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.00015 | $0.00906 |
| Opus 5 | $0.00008 | $0.00453 |
| Sonnet 5 | $0.00003 | $0.00181 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
arch-fitness 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-fitness — 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/arch-fitness {repo|path}
Define y ejecuta reglas de integridad arquitectónica (fitness functions) para un proyecto.
Prerequisitos
- Repositorio accesible
- Recomendado: ejecutar
/arch-detectprimero
2. Cargar perfil de usuario
- Leer
.claude/profiles/active-user.md→ obteneractive_slug - Si hay perfil activo, cargar (grupo Architecture & Debt del context-map):
profiles/users/{slug}/identity.mdprofiles/users/{slug}/projects.mdprofiles/users/{slug}/preferences.md
- Adaptar profundidad del análisis según
preferences.detail_level - Si no hay perfil → continuar con comportamiento por defecto
3. Parámetros
{repo|path}— Ruta local o repositorio--rules {file}— (Opcional) Fichero custom de reglas--fix— (Opcional) Sugerir fixes automáticos
4. Flujo de Ejecución
1. Detectar Patrón y Lenguaje
Si no hay detección previa, ejecutar detección rápida (solo estructura). Cargar reglas base del patrón detectado.
2. Definir Reglas de Fitness
Reglas automáticas según patrón:
Clean Architecture / Hexagonal:
- CRITICAL: Domain NO importa Infrastructure
- CRITICAL: Domain NO importa Presentation
- WARNING: Application NO importa Presentation directamente
- WARNING: No dependencias circulares entre capas
DDD:
- CRITICAL: Aggregates solo accesibles via Repository
- WARNING: Value Objects son inmutables (no setters públicos)
- WARNING: Domain Events nombrados en pasado (OrderCreated, UserRegistered)
MVC / MVVM:
- WARNING: Controllers/ViewModels NO acceden a DB directamente
- WARNING: Views NO contienen lógica de negocio
- CRITICAL: Models NO dependen de Views
Genéricas (todos los patrones):
- WARNING: No ficheros >300 líneas (configurable)
- WARNING: No más de 10 imports/dependencias por fichero
- CRITICAL: No secrets hardcodeados (regex patterns)
- WARNING: Naming conventions del patrón (sufijos esperados)
3. Ejecutar Análisis
Para cada regla:
- Escanear ficheros relevantes
- Buscar violaciones (imports, naming, estructura)
- Clasificar: PASS / FAIL
- Si FAIL: listar ficheros y líneas
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 · 119 lines · 15 tokens per session scan A 3e491e92f1b7
arch-fitness is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 15 tokens to every session and 906 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-fitness, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
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…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.