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 instructions/developmentagentsdd/mcp-jiracloud/agents-mdgit 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.00504 | $0.00504 |
| Opus 5 | $0.00252 | $0.00252 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
MCP-JiraCloud AGENTS.md 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.
What it actually says
AGENTS.md
Harness Engineering para Microservicios .NET Core
Este proyecto utiliza ingenieria de arneses con opencode para orquestar el ciclo de vida completo de microservicios .NET Core.
Estructura
.opencode/
agents/
leader.md # Agente lider (orquestador principal)
analysis.md # Analisis DDD y requerimientos
architect.md # Definicion arquitectonica (architecture.md + ADR)
design.md # Contratos API, modelo de datos, integracion
scaffold.md # Scaffolding de solucion y proyectos
develop.md # Implementacion y codificacion
test.md # Estrategia de pruebas
quality.md # Calidad de codigo y seguridad
deploy.md # CI/CD, infraestructura, despliegue
features.md # Gestion de features, backlog, ramas, estado
skills/
dotnet-microservice/ # Convenciones .NET Core y stack tecnologico
SKILL.md
tdd/ # Test-Driven Development (RED-GREEN-REFACTOR)
SKILL.md
bdd/ # Behavior-Driven Development (Gherkin + SpecFlow)
SKILL.md
git-flow/ # Estrategia de branching Git Flow
SKILL.md
Uso
- Inicia con el agente lider para tareas integrales de microservicio
- Cada fase del SDLC tiene un subagente especializado
- Los subagentes son invocados automaticamente por el lider segun la fase
- Los artefactos generados se almacenan en
docs/ysrc/segun corresponda
Instrucciones generales
- Siempre usar
dotnetCLI para operaciones .NET - Seguir Clean Architecture y principios SOLID
- Stack por defecto: .NET (ultima version LTS), EF Core, PostgreSQL, MediatR, Docker, Kubernetes
- Generar siempre health checks, logging estructurado y metricas
- Usar estrategia Git Flow: cada feature en su propia rama
feature/{id}-{slug} - Aplicar TDD (skill
tdd) en implementacion y BDD (skillbdd) en criterios de aceptacion - Mantener vivo
docs/architecture.mdcon ADRs actualizados via agentearchitect
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 · 49 lines · 504 tokens per session scan A 172243773ca8
MCP-JiraCloud AGENTS.md is an instructions file published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 2mo ago), licensed MIT. It adds 504 tokens to every session, about $0.0025 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.