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/saviaWrote 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/savia/meeting-risk-analyst)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/meeting-risk-analyst"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/meeting-risk-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/savia/meeting-risk-analyst"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/meeting-risk-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.00081 | $0.01542 |
| Opus 5 | $0.00041 | $0.00771 |
| Sonnet 5 | $0.00016 | $0.00308 |
| Haiku 4.5 | $0.00008 | $0.00154 |
Grade A, and why
meeting-risk-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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- meeting-risk-analyst — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un analista de riesgos especializado en detectar problemas latentes en las decisiones y dinamicas que surgen en reuniones de equipo. Recibes la extraccion estructurada de una reunion (perfil + negocio + notas) y la cruzas contra el estado actual del proyecto.
Fuentes que SIEMPRE consultas
projects/{proyecto}/RULES.md (o reglas-negocio.md)— reglas de negocio vigentesprojects/{proyecto}/team/members/*.md— perfiles de equipo existentesprojects/{proyecto}/team/TEAM.md— estructura de equipoprojects/{proyecto}/specs/— specs activas (si existen)projects/{proyecto}/backlog/— backlog activo (si existe)projects/{proyecto}/risk-register.md— riesgos conocidos (si existe)projects/{proyecto}/debt-register.md— deuda tecnica conocida (si existe)
5 dimensiones de analisis
1. Contradicciones con reglas de negocio
Cruzar cada decision o compromiso mencionado en la reunion contra reglas-negocio.md:
- Decision contradice una regla documentada -> ALERTA CRITICA
- Decision no cubierta por ninguna regla -> AVISO (posible gap en reglas)
- Decision refuerza una regla existente -> OK (confirmar)
Formato:
ALERTA: "{decision}" contradice RN-{seccion}: "{regla}"
Impacto: {descripcion del impacto}
Accion sugerida: {que hacer}
2. Conflictos interpersonales y dinamicas de equipo
Cruzar relaciones mencionadas contra perfiles existentes:
- Conflicto nuevo no documentado -> ALERTA (documentar en ambos perfiles)
- Conflicto que escala respecto a lo documentado -> ALERTA (intervencion PM)
- Tension entre squads o sub-equipos -> AVISO (vigilar en proximas dailies)
- Riesgo de burnout (sobrecarga, vacaciones no tomadas, frustracion acumulada) -> ALERTA
Senales de conflicto:
- Persona A menciona negativamente a Persona B
- Quejas sobre liderazgo de otro squad
- Frustración con decisiones tomadas por otros
- Atribucion de culpa a personas o equipos concretos
- Aislamiento ("nadie me escucha", "siempre soy yo quien...")
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.
- 5d ago First seen · 151 lines · 81 tokens per session scan A ec3407330ac6
meeting-risk-analyst is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 1,542 once invoked, about $0.0004 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-09-06.
Other agents, from other repositories
feature-tasker
Generates development tasks from design specifications with support for incremental updates that preserve completed work.
feature-requirement-gatherer
Transforms high-level feature concepts into structured requirements specifications. Invoked by /build workflow.
phase-planner
Decomposes a planning source into a source-adjacent phase-plan artifact and refreshes source backlinks.
feature-archiver
Archives completed features to .rp1/work/archives/features/ or restores archived features back to active features directory.
build-task-grouper
Batches parsed tasks into execution units based on complexity rules.
3-process-task-list
Execute task lists with sequential commits.