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/mizukaizen/hive-doctrine-mcpWrote 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/commands/mizukaizen/hive-doctrine-mcp/generate-tests)<a href="https://agentmods.dev/commands/mizukaizen/hive-doctrine-mcp/generate-tests"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/generate-tests/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/commands/mizukaizen/hive-doctrine-mcp/generate-tests"><img src="https://agentmods.dev/badge/commands/mizukaizen/hive-doctrine-mcp/generate-tests.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.00000 | $0.00575 |
| Opus 5 | $0.00000 | $0.00287 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
generate-tests 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 10d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/generate-tests
Generate tests for changed files — unit tests for functions, integration tests for APIs, E2E for user flows.
Usage
/generate-tests [--scope "changed|file|directory"] [--target "<path>"] [--types "unit,integration,e2e"] [--framework "jest|pytest|vitest|mocha"]
Behaviour
1. Identify What Changed
- changed (default): Run
git diff --name-onlyto find modified files. Focus testing on these. - file: Generate tests for the specific file at
--target. - directory: Generate tests for all source files in the
--targetdirectory.
2. Analyse the Code
For each file:
- Identify exported functions, classes, and methods
- Determine input types and return types
- Identify side effects (database calls, API calls, file operations)
- Identify error handling paths
- Map dependencies that need mocking
3. Generate Tests
Unit tests for each function:
- Happy path with typical input
- Edge cases (empty input, null, boundary values)
- Error cases (invalid input, missing dependencies)
- Each test follows AAA pattern
- Mock external dependencies
Integration tests for API endpoints and service interactions:
- Request/response contract tests
- Authentication and authorisation tests
- Error response format tests
- Rate limiting and validation tests
E2E tests (only when --types includes "e2e"):
- User workflow tests for the affected feature
- Smoke tests for critical paths that might be affected
4. Place Tests
Follow the project's existing test structure. If none exists:
- Unit tests:
tests/unit/[matching-source-path].test.[ext] - Integration tests:
tests/integration/[feature].test.[ext] - E2E tests:
tests/e2e/[workflow].test.[ext]
5. Output
Display a summary:
Tests generated:
Unit: 12 tests across 3 files
Integration: 4 tests across 1 file
E2E: 0 tests (not requested)
Files created:
tests/unit/auth/login.test.ts
tests/unit/auth/validate-token.test.ts
tests/unit/utils/format-date.test.ts
tests/integration/auth-api.test.ts
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.
- 10d ago First seen · 75 lines · 0 tokens per session scan A 8bf70d784f0f
generate-tests is a command published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 575 tokens. 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 commands, from other repositories
ui-aqa-flow-code-analysis
Phase 3 Code Analysis of ui-aqa-flow.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
test-suite
Run comprehensive test suite with coverage analysis.
testing
Comprehensive testing through distributed execution.
test
Escrever e rodar testes (skill 05 — QA Engineer).
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.