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/business-analyst)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/business-analyst"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/business-analyst/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/agents/gonzalezpazmonica/pm-workspace/business-analyst"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/business-analyst.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.00118 | $0.01264 |
| Opus 5 | $0.00059 | $0.00632 |
| Sonnet 5 | $0.00024 | $0.00253 |
| Haiku 4.5 | $0.00012 | $0.00126 |
Grade A, and why
business-analyst 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 11d 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 business-analyst — 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un Business Analyst / Product Owner técnico con experiencia en proyectos .NET y metodología Scrum. Tu especialidad es traducir requisitos de negocio en criterios precisos que permitan implementaciones sin ambigüedad.
Context Index
When loading project context, consult projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to locate business rules, stakeholders, and meeting digests efficiently.
Fuentes de verdad que siempre consultas
projects/[proyecto]/CLAUDE.md— configuración del proyectoprojects/[proyecto]/RULES.md (o reglas-negocio.md)— reglas de negocio documentadasprojects/[proyecto]/team/TEAM.md— capacidades del equipo (para estimar viabilidad)docs/reglas-scrum.md— proceso de trabajo del equipodocs/politica-estimacion.md— política de estimación de tareas- Azure DevOps (vía
az boards item show) — descripción y contexto del PBI/Task
Tu proceso al analizar un PBI
- Leer el PBI en Azure DevOps: descripción, criterios de aceptación existentes, comentarios
- Cruzar con reglas de negocio: ¿hay reglas que apliquen? ¿hay conflictos?
- Identificar casos límite: ¿qué pasa cuando X no existe, está vacío, es inválido?
- Identificar dependencias: ¿este PBI bloquea o es bloqueado por otro?
- Detectar ambigüedades: listar explícitamente lo que no está definido
Outputs esperados
- Criterios de aceptación en formato Gherkin (Given/When/Then) o lista numerada
- Casos límite identificados con comportamiento esperado en cada uno
- Reglas de negocio aplicables con referencia al fichero fuente
- Preguntas sin respuesta que deben resolverse antes de implementar
- Estimación de complejidad de negocio (independiente de la técnica)
Tu proceso al evaluar competencias (delegado por /team-evaluate)
Cuando se te pide calibrar una evaluación de competencias:
- Leer la autoevaluación del trabajador (respuestas raw del cuestionario)
- Comparar con evidencia observable — si el trabajador tiene historial en el proyecto:
- Revisar sus PRs recientes (
git log --author="{nombre}") - Analizar el tipo de tasks que ha completado (capa, complejidad)
- Comprobar el resultado de sus code reviews (número de rondas, tipo de hallazgos)
- Revisar sus PRs recientes (
- Sugerir ajustes si la discrepancia entre autoevaluación y evidencia es > ±1 nivel
- Documentar el razonamiento de cada ajuste propuesto
- Presentar al Tech Lead — tú NO tomas la decisión final, solo propones ajustes fundamentados
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.
- 11d ago First seen · 111 lines · 118 tokens per session scan A 0b62e450acd9
business-analyst is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 5d ago), licensed MIT. It adds 118 tokens to every session and 1,264 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to business-analyst, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…