What is adoption-sandbox?

A safe practice environment with fictional projects, sprints, work items, and team data. A sandbox is an isolated area where experiments do not affect real systems or repositories.

Use it to practise commands, explore templates and diagrams, and experiment with sprint and work-item workflows using dummy data.

It lets developers and project managers learn Savia commands without changing real Azure DevOps data or creating commits. Feedback can be tested against sample workflows first.

adoption-sandbox — Command for Claude Code by gonzalezpazmonica

Install

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.

Clone the repo

git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspace

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/adoption-sandbox/github.svg)](https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/adoption-sandbox)

Your own site

<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/adoption-sandbox"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/adoption-sandbox/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/adoption-sandbox"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/adoption-sandbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 871 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00019	$0.00871
Opus 5	$0.00010	$0.00436
Sonnet 5	$0.00004	$0.00174
Haiku 4.5	$0.00002	$0.00087

Measured 8d ago against content hash 00b31c0fe5b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

adoption-sandbox 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 8d 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.

Origin

This is a copy

100% identical to adoption-sandbox — 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.

.claude/commands/adoption-sandbox.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/adoption-sandbox

🦉 "Prueba todo, no pasa nada." Sandbox aislado con datos ficticios.

Experimentar libremente sin riesgo: datos de prueba, sin Azure DevOps real, sin commits.

Objetivo

Que los devs y PMs practiquen comandos de Savia con total seguridad antes de usarlos en producción. Feedback inmediato. Sin estrés.

Estructura del Sandbox

sandbox/
├── projects/
│   └── sandbox-demo/
│       ├── CLAUDE.md                ← Config sandbox
│       ├── equipo.md                ← Team ficticio
│       ├── reglas-negocio.md        ← Domain model ficticio
│       └── data/
│           ├── sprints.json         ← Sprint data ficticios
│           ├── work-items.json      ← PBIs/Tasks ficticias
│           └── board-state.json     ← Board snapshot
├── docs/
│   └── sandbox-guide.md             ← Guía de qué experimentar
└── .env.sandbox                     ← Vars de entorno sandbox

Flujo

Paso 1 — Crear sandbox project

Crear projects/sandbox-demo/ con estructura estándar
Generar datos de prueba: 2 sprints ficticios, 20 PBIs, 5 personas
Configura AZURE_DEVOPS_PROJECT en .env.sandbox → null/offline
Copiar plantillas de specs, diagramas, para experimentar

Paso 2 — Habilitar comandos en "safe mode"

Todos los comandos ejecutan pero NO afectan:
- Azure DevOps real (queries simuladas)
- Repos reales (cambios en memoria, no commits)
- Informes reales (generados en sandbox/output/)
Mostrar banner: ⚠️ SANDBOX MODE — cambios no persisten

Paso 3 — Invitar a experimentar

"Intenta /sprint-status aquí — sin riesgo"
"Crea un PBI ficticio con /pbi-create"
"Genera una spec ficticia con /spec-generate"
"Escribe código en el sandbox sin commits"
Feedback inmediato: ✅ esto funcionaría, 🔴 aquí te equivocarías

Paso 4 — Rastrear experimentos

Log: sandbox/usage-log.json con cada comando ejecutado
Qué intentó: suceso/error
Duración: ¿rápido o lento?
Feedback: ¿comprensible? ¿útil?

Paso 5 — Feedback post-sesión

Resumen: "Ejecutaste 12 comandos, 11 éxito, 1 confusión"
Áreas de mejora: "La /pbi-create podría ser más clara"
Siguiente paso: "¿Listo para usar esto en tu proyecto real?"

Read the full file on GitHub · 105 lines

Changes

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.

8d ago First seen · 105 lines · 19 tokens per session scan A 00b31c0fe5b7

Subscribe to this mod's changes

adoption-sandbox is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 19 tokens to every session and 871 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-sandbox, differing in 0 lines, and is treated as a copy.

Learning and teaching Testing

adoption-sandbox