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 skills/developmentagentsdd/mcp-jiracloud/bddnpx skills add DevelopmentAgentSDD/MCP-JiraCloud --skill bddgit clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloudWrote 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/skills/developmentagentsdd/mcp-jiracloud/bdd)<a href="https://agentmods.dev/skills/developmentagentsdd/mcp-jiracloud/bdd"><img src="https://agentmods.dev/badge/skills/developmentagentsdd/mcp-jiracloud/bdd.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 | $0.00052 | $0.00600 |
| Opus 5 | $0.00026 | $0.00300 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
bdd 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 3d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BDD — Behavior-Driven Development para .NET Core
Flujo BDD
Descubrimiento -> Formulacion -> Automatizacion
1. Descubrimiento — Refinar requisitos con ejemplos concretos
Realizar sesiones de Example Mapping o Specification by Example con stakeholders.
2. Formulacion — Escribir en Gherkin
# features/orders/create_order.feature
Feature: Crear pedido
Scenario: Pedido valido con items en stock
Given un producto "Laptop" con stock 10 y precio 1500 USD
And un cliente autenticado con id "C001"
When el cliente crea un pedido con 2 unidades de "Laptop"
Then el pedido se registra con estado "Pendiente"
And el total del pedido es 3000 USD
And el stock de "Laptop" se reduce a 8
Scenario: Cantidad negativa rechazada
When el cliente intenta crear un pedido con -3 unidades de "Laptop"
Then el sistema rechaza con error "Order.Quantity.Negative"
3. Automatizacion — Implementar step definitions
[Binding]
public class CreateOrderSteps
{
private readonly IOrderRepository _repo;
private readonly IMediator _mediator;
private Result<OrderDto> _result;
[Given(@"un producto ""(.*)"" con stock (\d+) y precio (\d+) USD")]
public async Task GivenProductWithStockAndPrice(string name, int stock, decimal price) { ... }
[When(@"el cliente crea un pedido con (\d+) unidades de ""(.*)""")]
public async Task WhenClientCreatesOrder(int qty, string product) { ... }
[Then(@"el pedido se registra con estado ""(.*)""")]
public void ThenOrderRegisteredWithStatus(string status) { ... }
}
Herramientas
| Herramienta | Proposito |
|---|---|
| Reqnroll (antes SpecFlow) | Engine BDD para .NET |
| Gherkin | Lenguaje de especificacion |
| xUnit | Runner de pruebas (integrado con Reqnroll) |
| FluentAssertions | Aserciones en step definitions |
Reglas
- Un archivo
.featurepor feature de negocio - Cada scenario debe ser independiente (no compartir estado entre scenarios)
- Mantener los step definitions reusables (usar parametros, no duplicar)
- Las pruebas BDD son pruebas de aceptacion, no unitarias: validan el sistema completo
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.
- 3d ago First seen · 73 lines · 52 tokens per session scan A 0e5bb8f4c41c
bdd is a skill published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 600 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…