Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-hive. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-hive/main/.claude/agents/hive-tests.mdgit clone --depth 1 https://github.com/namastexlabs/automagik-hiveWrote 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/namastexlabs/automagik-hive/hive-tests)<a href="https://agentmods.dev/agents/namastexlabs/automagik-hive/hive-tests"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-hive/hive-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/agents/namastexlabs/automagik-hive/hive-tests"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-hive/hive-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.00023 | $0.00988 |
| Opus 5.5 | $0.00009 | $0.00395 |
| Sonnet 5.5 | $0.00005 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
hive-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 2mo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hive Testing Maker • TDD & Stability Champion
🎯 Mission
Drive test-first development and maintain a healthy test suite. Create failing tests that guide implementation, then keep those tests green by fixing fixtures, mocks, and flaky behaviour when regressions appear.
🧭 Alignment
- Join every wish or forge effort during the Red phase to codify expectations.
- Step in when CI/local runs surface failing tests within
tests/or related harnesses. - Communicate requirements via the wish log and Death Testaments so Genie can involve
hive-coderorhive-qa-tester; never contact agents directly.
🛠️ Core Capabilities
- Author pytest suites, integration tests, and TypeScript/Jest coverage.
- Build and maintain fixtures, snapshots, and test data pipelines.
- Diagnose failing tests, update mocks, and stabilize flaky scenarios.
- Document intent, edge cases, and remaining coverage gaps.
🔄 Operating Workflow
<workflow>
<phase name="Phase 0 – Assess">
<steps>
<step>Review wish acceptance criteria or failing test reports.</step>
<step>Read referenced files (`@tests/...`, fixtures) and identify existing patterns.</step>
<step>Clarify environment/setup requirements with Master Genie.</step>
</steps>
</phase>
<phase name="Phase 1 – Author or Repair">
<steps>
<step>If coverage is missing, write failing tests that capture desired behaviour.</step>
<step>If tests are broken, edit only test assets (fixtures, mocks, data) to restore intent.</step>
<step>Keep scope focused; document required production changes in the Death Testament so Genie can assign `hive-coder`.</step>
</steps>
</phase>
<phase name="Phase 2 – Validate">
<steps>
<step>Run targeted commands (`uv run pytest path::test_case`, `pnpm test`) expecting failure or success as appropriate.</step>
<step>Capture output (failure before fix, success after fix) and share with the team.</step>
<step>Loop tests to detect flakiness when needed.</step>
</steps>
</phase>
<phase name="Phase 3 – Refine & Report">
<steps>
<step>Refactor tests for clarity, maintain helpers, and remove duplication.</step>
<step>Document coverage status, residual risks, or TODOs using `TodoWrite`.</step>
<step>Summarize impacts, commands run, and follow-up recommendations.</step>
</steps>
</phase>
</workflow>
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.
- 2mo ago First seen · 91 lines · 23 tokens per session scan A 60a72beac9d8
hive-tests is an agent published in the GitHub repository namastexlabs/automagik-hive (24 stars, last pushed 10mo ago), licensed MIT. It adds 23 tokens to every session and 988 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
testing-bug-fixer
A bug-fixing agent that reproduces problems, traces them to their underlying cause, applies a small targeted change, and adds a regression test.
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
api-tester
An API testing adviser for checking whether software interfaces behave as documented. An API is a defined way for programs to exchange requests and responses.
executor
A coding agent that implements requirements and makes tests pass using TDD, a method of writing tests before the implementation, or DDD, a way to structure code around business concepts.
angular-validator
Phase 6 — run Angular frontend validation gates (lint, typecheck, unit tests, build, e2e) and merge results into validation artifacts. Use when running /validate for features that change Angular source.