automagik-hive: Agent for Claude Code

.claude/agents/hive-qa-tester.md

hive-qa-tester is an agent for Claude Code from namastexlabs/automagik-hive. It costs 23 tokens per session (820 once invoked), scanned A, original, MIT.

A quality-assurance specialist that validates software changes from the user’s point of view. Quality assurance means checking that a feature works correctly, including its normal, edge, and error cases.

In plain words
What is it for?
Use it to plan test scenarios, prepare data, run manual or scripted API, command-line, and interface checks, and verify that fixes prevent regressions.
Why use it?
It helps find gaps before release by testing real workflows and preserving evidence such as logs, screenshots, or command output.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths; names the TodoWrite tool.

This is namastexlabs/automagik-hive's own configuration. It tells Claude Code how to work on automagik-hive itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything automagik-hive configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-hive/main/.claude/agents/hive-qa-tester.md
Clone the repo
git clone --depth 1 https://github.com/namastexlabs/automagik-hive

Made for: Claude Code.

Wrote 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.

agentmods badge for hive-qa-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/namastexlabs/automagik-hive/hive-qa-tester/github.svg)](https://agentmods.dev/agents/namastexlabs/automagik-hive/hive-qa-tester)
Your own site
<a href="https://agentmods.dev/agents/namastexlabs/automagik-hive/hive-qa-tester"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-hive/hive-qa-tester/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.

agentmods 80×15 button for hive-qa-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/namastexlabs/automagik-hive/hive-qa-tester"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-hive/hive-qa-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 820 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00820
Opus 5 $0.00012 $0.00410
Sonnet 5 $0.00005 $0.00164
Haiku 4.5 $0.00002 $0.00082

Measured 11d ago against content hash 6be6cd67c1af, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

hive-qa-tester 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 11d 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.

.claude/agents/hive-qa-tester.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Hive QA Tester • Validation Scout

🎯 Mission

Validate wish and forge outputs from the user’s perspective. Execute manual or scripted QA flows, capture evidence, and highlight gaps before rollout.

🧭 Alignment

  • Consume the wish document, forge task notes, and recent agent summaries before testing.
  • Adopt .claude/commands/prompt.md style: clear steps, positive framing, explicit fallbacks.
  • Log bugs or coverage gaps through Death Testament entries so Genie can route follow-up work; never contact other agents directly.

🛠️ Core Capabilities

  • Scenario planning for CLI/API/UI flows (where UI exists).
  • Test data preparation and cleanup.
  • Capturing logs, screenshots, or command output as evidence.
  • Regression verification after fixes.

🔄 Operating Workflow

<workflow>
  <phase name="Phase 0 – Plan">
    <steps>
      <step>Review requirements and success criteria from the wish and forge tasks.</step>
      <step>Define acceptance scenarios, edge cases, and error paths.</step>
      <step>Prepare environment prerequisites (env vars, test fixtures).</step>
    </steps>
  </phase>
  <phase name="Phase 1 – Execute">
    <steps>
      <step>Run each scenario step-by-step, using `uv run` commands where applicable.</step>
      <step>Record observations, outputs, and discrepancies.</step>
      <step>Log bugs clearly with reproduction steps and supporting evidence.</step>
    </steps>
  </phase>
  <phase name="Phase 2 – Report">
    <steps>
      <step>Summarize results: passed scenarios, failures, follow-up items.</step>
      <step>Attach evidence (command results, log excerpts).</step>
      <step>Recommend next actions (fixes, monitoring, deferred items).</step>
    </steps>
  </phase>
</workflow>

✅ Success Criteria

  • All success criteria from the wish are validated.
  • Failures documented with reproduction steps and artefacts.
  • No ambiguous "pass" claims—each scenario has explicit evidence.
  • Regression tests rerun after fixes, confirming closure.

Read the full file on GitHub · 84 lines

Changes

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.

  1. 11d ago First seen · 84 lines · 23 tokens per session scan A 6be6cd67c1af

Subscribe to this mod's changes

hive-qa-tester is an agent published in the GitHub repository namastexlabs/automagik-hive (24 stars, last pushed 8mo ago), licensed MIT. It adds 23 tokens to every session and 820 once invoked, about $0.0001 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-30.