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/company-vertical)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/company-vertical"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/company-vertical/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/company-vertical"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/company-vertical.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.00023 | $0.00722 |
| Opus 5 | $0.00012 | $0.00361 |
| Sonnet 5 | $0.00005 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
company-vertical 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 7d 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 company-vertical — 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/company-vertical
🦉 Savia adapta pm-workspace a las necesidades de tu industria.
Cargar perfil de usuario
Grupo: Infrastructure — cargar:
identity.md— nombre, rolcompany/identity.md— sector de la empresacompany/vertical.md— vertical actual (si existe)
Subcomandos
/company-vertical detect— detectar vertical desde el contexto del proyecto/company-vertical configure {sector}— configurar vertical manualmente/company-vertical regulations— listar regulaciones aplicables/company-vertical best-practices— mejores prácticas PM del sector
Flujo
Paso 1 — Detectar o confirmar vertical
Analizar company/identity.md y proyectos activos para inferir sector.
Verticales soportadas (ampliando v0.37.0):
Verticales con compliance específico:
├─ healthcare — HIPAA, HL7 FHIR, FDA 21 CFR Part 11
├─ finance — SOX, Basel III, MiFID II, PCI DSS
├─ legal — GDPR, eDiscovery, legal hold
├─ education — FERPA, accesibilidad educativa
├─ government — FedRAMP, NIST 800-53
└─ defense — ITAR, CMMC
Verticales con frameworks PM:
├─ construction — PMBOK heavy, Earned Value
├─ manufacturing — Lean, Six Sigma, ISO 9001
├─ retail — seasonal planning, demand forecasting
├─ media — creative workflows, content calendars
├─ logistics — supply chain, just-in-time
└─ energy — safety-critical, ISO 55000
Paso 2 — Configurar regulaciones
📋 Regulaciones detectadas para {sector}
Obligatorias:
├─ {reg1} — {descripción breve}
└─ {reg2} — {descripción breve}
Recomendadas:
├─ {reg3} — {descripción breve}
└─ {reg4} — {descripción breve}
¿Activar compliance automático? [S/n]
Paso 3 — Adaptar mejores prácticas
Cargar frameworks PM específicos del sector:
- Ceremonias adaptadas (ej: healthcare necesita review de PHI)
- Métricas específicas (ej: finanzas necesita audit trail)
- Templates de documentación del sector
Paso 4 — Guardar en vertical.md
Actualizar .claude/profiles/company/vertical.md.
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.
- 7d ago First seen · 109 lines · 23 tokens per session scan A 51a84a32aa74
company-vertical is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 722 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 company-vertical, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
company-vertical
Detectar y configurar la vertical de la empresa — regulaciones, frameworks y mejores prácticas del sector.
/accreditation-track
Seguimiento de acreditaciones sanitarias (JCI, EFQM, ISO 9001, ISO 15189). Mapea requisitos a evidencias, detecta gaps, genera reportes de cumplimiento. Prepara auditorías y evaluaciones de terceros.
audit-trail
Generar y consultar el log de auditoría de decisiones asistidas por IA. Usa cuando el usuario dice "audit trail", "decision log", "log de decisiones", "AI decisions", "audit log", "追溯", "track decisions", "quien decidió qué", "decision history". Registra y consulta el log de decisiones tomadas durante la sesión.
service-assessment
Prepare for GDS Service Standard assessment - analyze evidence against 14 points, identify gaps, generate readiness report.
dos
Generate Digital Outcomes and Specialists (DOS) procurement documentation for UK Digital Marketplace.
risk
Create comprehensive risk register following HM Treasury Orange Book principles.