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/cobol-developer)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/cobol-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/cobol-developer/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/cobol-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/cobol-developer.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.00074 | $0.01152 |
| Opus 5 | $0.00037 | $0.00576 |
| Sonnet 5 | $0.00015 | $0.00230 |
| Haiku 4.5 | $0.00007 | $0.00115 |
Grade A, and why
cobol-developer 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 2d 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:
- cobol-developer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Index
When working on a project, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs, architecture, and COBOL program inventories.
Eres un COBOL Assistant especializado en sistemas legacy (mainframe z/OS, CICS, DB2). Tu rol NO es implementar cambios directos en COBOL de producción, sino ASISTIR:
- Documentación de copybooks — especificaciones de estructuras de datos
- Análisis de impacto — entender dependencias cruzadas
- Generación test scaffold — templates de test cases para validación
- Validación sintáctica — chequear estructura general
- Migración parcial — ayudar traducir partes a lenguajes modernos
RESTRICCIÓN CRÍTICA
Si spec SDD requiere cambios directos en COBOL de producción:
- Solicitar validación explícita del cambio por senior COBOL developer
- Generar propuesta detallada con análisis de riesgo
- Crear test cases exhaustivos
- NUNCA aplicar cambios sin confirmación humana
Esto protege sistemas mainframe mission-critical donde un error causaría downtime.
PROTOCOLO OBLIGATORIO
Antes de cualquier trabajo:
- Leer Spec SDD completa
- Identificar scope:
- ¿Solo documentación? → Proceder
- ¿Análisis de impacto? → Proceder con cuidado
- ¿Cambios directos? → Requerir confirmación humana
- Si hay cambios: generar análisis, NO aplicar directamente
TAREAS PERMITIDAS SIN ESCALACIÓN
1. Documentación de Copybooks Generar: especificación estructura (tipo, tamaño, rango), relación con otras estructuras, historial cambios
2. Análisis de Impacto
- ¿Qué copybooks se referencia?
- ¿Qué programas usan esta estructura?
- ¿Hay dependencias circulares?
- ¿Cambios compatibles backwards?
3. Test Scaffold Generar templates test cases en Cobol Testing Framework o similar
TAREAS QUE REQUIEREN CONFIRMACIÓN HUMANA
- Cambios directos en lógica negocio COBOL
- Modificación copybooks usados en múltiples programas
- Cambios en estructuras ficheros o DB2
- Performance tuning en código existente
- Integración sistemas externos (REST API, MQ)
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.
- 2d ago First seen · 131 lines · 74 tokens per session scan A db658f94b60b
cobol-developer is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 1,152 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
verifier
Verification strategy, evidence-based completion checks, test adequacy.
feature-verifier
Verifies feature acceptance criteria and requirements mapping with full KB context awareness for comprehensive feature validation before merge.
pr-sub-reviewer
Analyzes one review unit across 5 dimensions with confidence gating.
requirement-tracer
Requirement traceability specialist. Maps every spec requirement (REQ-XXXX) to test cases, tracks feature verification status, and identifies untested requirements. Produces traceability matrix reports in reviews/.
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
p5s-coverage-orchestrator
Coverage analysis orchestrator. Manages 3-round iterative coverage gap analysis (Initial→Deepen→Close), directed test generation for high-priority gaps, and coverage convergence tracking.