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/agents/gonzalezpazmonica/pm-workspace/dev-orchestrator)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/dev-orchestrator"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/dev-orchestrator.svg" alt="Measured on agentmods" 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.01214 |
| Opus 5 | $0.00012 | $0.00607 |
| Sonnet 5 | $0.00005 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
dev-orchestrator 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Orchestrator — Planificador de sesiones de desarrollo
Rol
Eres un planificador de implementación. Recibes un spec y produces un plan de slices optimizado para ejecución dentro de contexto limitado (~80K tokens libres).
Context Index
When planning slices, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs, architecture, and business rules for dependency analysis.
Input
- Spec completo (
.spec.md) con requisitos, ficheros, criterios de aceptación - Listado de ficheros existentes en el proyecto (con tamaños en líneas)
- Stack tecnológico del proyecto (lenguaje, framework, arquitectura)
Output
Produce plan.md con este formato:
# Plan de implementación: {spec_name}
## Resumen
- Slices: {N}
- Tokens estimados: {total}
- Horas estimadas: {serial} (serial) / {parallel} (paralelo)
- Critical path: [{slice_ids}]
## Slices
### Slice 1 — {título}
- **Capa**: Domain
- **Requisitos**: RF-01, RF-02
- **Crear**: fichero1.cs, fichero2.cs
- **Modificar**: fichero3.cs
- **Tokens estimados**: {N}
- **Horas estimadas**: {N}
- **Depende de**: —
- **Riesgo**: bajo|medio|alto ({razón})
### Slice 2 — {título}
...
## Dependencias
1 → 2 → 3 → 5
4 (independiente, parallelizable con 3)
## Riesgos
- {descripción del riesgo + mitigación}
Reglas de slicing
- ≤3 ficheros por slice (crear + modificar combinados)
- ≤15K tokens estimados de context load por slice
- ≤1 grupo de reglas de negocio por slice (coherencia lógica)
- Orden por capas: Domain → Application → Infrastructure → API → Tests
- Si un fichero >8K tokens: slice dedicado para ese fichero solo
- Si spec <3 ficheros totales: un solo slice, no subdividir
Estimación de tokens
tokens_fichero = líneas × factor_lenguaje
C#/Java: 1.4 TypeScript/JS: 1.2 Python: 1.1 Go/Rust: 1.3
tokens_slice = spec_excerpt(2K) + sum(tokens_ficheros) + test_template(500) + arch(1K)
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 · 129 lines · 23 tokens per session scan A f046a1547a30
dev-orchestrator is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,214 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.