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/adoption-plan)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/adoption-plan"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/adoption-plan/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/adoption-plan"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/adoption-plan.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.00021 | $0.00749 |
| Opus 5 | $0.00010 | $0.00375 |
| Sonnet 5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
adoption-plan 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 adoption-plan — 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/adoption-plan
🦉 Roadmap de aprendizaje personalizado: "Tú eres {rol}, empieza por aquí".
Cada rol tiene una ruta diferente para máxima productividad rápido.
Roles Soportados
- PM / Scrum Master — Sprint, backlog, reportes
- Tech Lead — Architecture, PRs, deuda técnica
- Developer — Code patterns, specs, workflows
- QA Engineer — Testing, coverage, regression
- Product Owner — Outcomes, value, stakeholder alignment
- DevOps — Infrastructure, pipelines, integrations
- CEO / CTO — Portfolio, metrics, strategy
Estructura de Learning Path
Nivel 1: Beginner (Semana 1-2)
├─ Comandos "watch-only" (no escriben en Azure DevOps)
├─ Dashboard viewing: /sprint-status, /team-workload, /qa-dashboard
└─ Goal: Familiaridad sin riesgo
Nivel 2: Intermediate (Semana 3-4)
├─ Comandos que leen + crean borradores
├─ PBI planning, spec generation, PR reviews
└─ Goal: Participación segura en sprint
Nivel 3: Advanced (Semana 5-8)
├─ SDD agent orchestration, infra provisioning
├─ Autonomía en fljos complejos
└─ Goal: Power user + mentor
Flujo
Paso 1 — Detectar rol del usuario
- Leer
identity.md(si existe) - Si no: preguntar interactivamente
Paso 2 — Cargar rol-workflow
- Por rol: consultar
@docs/rules/domain/role-workflows.md - Extraer comandos prioritarios para ese rol
Paso 3 — Seleccionar comandos por nivel
- L1 (Beginner): Top 3 comandos lectura pura
- L2 (Intermediate): Top 4 comandos lectura+escritura
- L3 (Advanced): Top 3 comandos complejos + skills
Paso 4 — Crear hitos y milestones
- Semana 1: Ejecutar todos L1 (6 comandos)
- Semana 2-3: Practicar L2 sin commit
- Semana 4: Usar L2 en sprint real
- Semana 5-8: L3 bajo supervisión → autonomía
- Métrica: "3 usos exitosos sin ayuda" = dominado
Paso 5 — Generar roadmap personal
- Fichero
adoption-plan-{rol}-{YYYYMMDD}.md - Incluir: comandos, orden, objetivos por semana, criterios éxito
- Sugerir: pairing sessions con mentor (si hay early adopters)
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 · 95 lines · 21 tokens per session scan A 9c1b49cffffc
adoption-plan is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 749 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 adoption-plan, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.