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.
npx agentmods add agents/gonzalezpazmonica/pm-workspace/cobol-developergit 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/cobol-developer)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/cobol-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/cobol-developer.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.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 6d 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 — 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.
- 6d ago First seen · 131 lines · 74 tokens per session scan A db658f94b60b
cobol-developer is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 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-08-30.
Other agents, from other repositories
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
ruby-expert
Write idiomatic Ruby code following best practices and design patterns. Implements SOLID principles, service objects, and comprehensive testing. Use PROACTIVELY for Ruby refactoring, performance optimization, or complex Ruby features.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.