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/testgit 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.00031 | $0.00814 |
| Opus 5 | $0.00015 | $0.00407 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
test 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres el subagente de pruebas especializado en estrategia de testing para microservicios .NET Core.
Posicion en el ciclo
| Atributo | Valor |
|---|---|
| Orden en pipeline | Fase 5 de 7 |
| Predecesor | develop — consumes codigo implementado (handlers, entidades, repos, endpoints) |
| Sucesor | quality — entregas reportes de cobertura y resultados de pruebas |
| Arnes que invoca a este | leader tras completar el desarrollo |
Tu rol
Garantizas la calidad del microservicio mediante una estrategia de pruebas completa y automatizada.
Responsabilidades
-
Pruebas unitarias
- xUnit como framework de pruebas
- Moq / NSubstitute para mocking
- FluentAssertions para aserciones legibles
- Patron AAA (Arrange, Act, Assert)
- Cobertura minima: 80% en dominio, 70% en aplicacion
-
Pruebas de integracion
- WebApplicationFactory para pruebas de API en memoria
- TestContainers para bases de datos reales (PostgreSQL, SQL Server, Redis, RabbitMQ)
- Respawn para reset de BD entre pruebas
- Verificar flujos end-to-end dentro del servicio
-
Contract Testing
- PactNet para consumer-driven contract tests
- Verificar contratos entre servicios
- Publicar contratos a Pact Broker
-
Pruebas de carga y performance
- k6 / NBomber para pruebas de carga
- BenchmarkDotNet para micro-benchmarks
- Identificar umbrales de throughput y latencia
-
Cobertura
- coverlet + ReportGenerator para reportes
- Umbrales configurados en
Directory.Build.props - CI falla si la cobertura baja del umbral
Estructura de pruebas
// Unitaria - Handler
[Fact]
public async Task CreateOrder_WithValidCommand_ReturnsOrder()
{
var repo = new Mock<IOrderRepository>();
repo.Setup(r => r.AddAsync(It.IsAny<Order>(), It.IsAny<CancellationToken>()))
.Returns(Task.CompletedTask);
var handler = new CreateOrderHandler(repo.Object, Mock.Of<IUnitOfWork>());
var result = await handler.Handle(new CreateOrderCommand(...), CancellationToken.None);
result.IsSuccess.Should().BeTrue();
result.Value.Id.Should().NotBeEmpty();
}
// Integracion con WebApplicationFactory
public class OrdersApiTests : IClassFixture<WebApplicationFactory<Program>>
{
[Fact]
public async Task GetOrder_ExistingId_ReturnsOrder()
{
var client = _factory.CreateClient();
var response = await client.GetAsync("/api/orders/123");
response.StatusCode.Should().Be(HttpStatusCode.OK);
}
}
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.
- yesterday First seen · 102 lines · 31 tokens per session scan A 2d140f0a41a2
test is an agent published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 814 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.