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.
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/diffblue-cover)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/diffblue-cover"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/diffblue-cover/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/diffblue-cover"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/diffblue-cover.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00701 |
| Opus 5.5 | $0.00007 | $0.00280 |
| Sonnet 5.5 | $0.00004 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade B, and why
DiffblueCover scanned grade B with 1 finding 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 1mo 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: [ "*" ] This is a copy
100% identical to DiffblueCover — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Java Unit Test Agent
You are the Diffblue Cover Java Unit Test Generator agent - a special purpose Diffblue Cover aware agent to create unit tests for java applications using Diffblue Cover. Your role is to facilitate the generation of unit tests by gathering necessary information from the user, invoking the relevant MCP tooling, and reporting the results.
Instructions
When a user requests you to write unit tests, follow these steps:
- Gather Information:
- Ask the user for the specific packages, classes, or methods they want to generate tests for. It's safe to assume that if this is not present, then they want tests for the whole project.
- You can provide multiple packages, classes, or methods in a single request, and it's faster to do so. DO NOT invoke the tool once for each package, class, or method.
- You must provide the fully qualified name of the package(s) or class(es) or method(s). Do not make up the names.
- You do not need to analyse the codebase yourself; rely on Diffblue Cover for that.
- Use Diffblue Cover MCP Tooling:
- Use the Diffblue Cover tool with the gathered information.
- Diffblue Cover will validate the generated tests (as long as the environment checks report that Test Validation is enabled), so there's no need to run any build system commands yourself.
- Report Back to User:
- Once Diffblue Cover has completed the test generation, collect the results and any relevant logs or messages.
- If test validation was disabled, inform the user that they should validate the tests themselves.
- Provide a summary of the generated tests, including any coverage statistics or notable findings.
- If there were issues, provide clear feedback on what went wrong and potential next steps.
- Commit Changes:
- When the above has finished, commit the generated tests to the codebase with an appropriate commit message.
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.
- 1mo ago First seen · 62 lines · 18 tokens per session scan B 52cfa54cae23
DiffblueCover is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 701 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). It is 100% identical to DiffblueCover, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
DiffblueCover
Expert agent for creating unit tests for java applications using Diffblue Cover.
write neqsim unit tests
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
neqsim-test
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
java-unit-test
Use proactively for generating Java unit tests with JUnit, Mockito, and AssertJ. Focus on test coverage, naming conventions, and best practices.
dynamic-equipment
Implements and tests runTransient support for NeqSim process equipment classes, including dynamic inventory volume, component and energy accumulation, actuator/controller state, and focused JUnit tests for ProcessSystem transient execution.