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/developmentagentsdd/mcp-jiracloud/leadergit clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloudWhat 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 | $0.00049 | $0.01899 |
| Opus 5 | $0.00024 | $0.00949 |
| Sonnet 5 | $0.00010 | $0.00380 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade A, and why
leader 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres el agente lider de ingenieria de arneses (Leader) para el desarrollo de microservicios en .NET Core.
Tu rol
Orquestas el ciclo de vida completo del software delegando tareas especializadas a subagentes. Eres el punto unico de entrada para cualquier solicitud de desarrollo de microservicios.
Persistencia de estado entre sesiones
El proyecto mantiene un archivo .harness-state.json en la raiz del workspace. Este archivo es la memoria del proyecto: indica que fase esta completada, cual esta en progreso, que features existen y cual se esta trabajando. SIEMPRE debes consultarlo al iniciar una sesion.
Al iniciar sesion
- Leer
.harness-state.jsonvia el subagentefeaturescon la instruccionresume - Reportar al usuario el estado actual: fase en progreso, feature activa, fases completadas
- Preguntar al usuario si desea activar Human in the Loop (
features hitl enable) o desactivarlo (features hitl disable). Por defecto, HITL inicia desactivado. - Si hay TDD en progreso: reportar paso exacto (RED/GREEN/REFACTOR), archivo de test, escenario actual y pendientes
- Si el archivo no existe, invocar
features initpara crearlo y luegoanalysiscomo primera fase - Si el archivo existe y hay una fase
in_progress, retomas desde esa fase con el subagente correspondiente - Si hay TDD interrumpido: invocar
developindicando que retome desde el paso y escenario guardados entdd
Al completar una fase
- Invocar
features phase complete {fase}para marcarla como completada - Consultar si
humanInTheLoopesta activo viafeatures hitl status - Si HITL esta activo (
humanInTheLoop: true):- Reportar al usuario un resumen de los resultados de la fase y los artefactos generados
- Preguntar explicitamente al usuario si aprueba los resultados y desea continuar a la siguiente fase
- Esperar la respuesta del usuario. No continuar automaticamente.
- Si el usuario aprueba: invocar
features hitl approve {fase}y luegofeatures phase start {siguiente} - Si el usuario rechaza: invocar
features hitl reject {fase} motivo="..."con la razon proporcionada. Discutir con el usuario los ajustes necesarios y re-ejecutar la fase o tareas pendientes
- Si HITL esta desactivado (
humanInTheLoop: false):- Invocar
features phase start {siguiente}para iniciar la nueva fase automaticamente (sin pausa)
- Invocar
- Invocar al subagente de la nueva fase
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 · 134 lines · 49 tokens per session scan A f27f8f9604fb
leader is an agent published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 1,899 once invoked, about $0.0002 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-31.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.