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-coder.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-coder)<a href="https://agentmods.dev/agents/namastexlabs/automagik-hive/hive-coder"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-hive/hive-coder.svg" alt="Measured on agentmods" 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.00022 | $0.01128 |
| Opus 5 | $0.00011 | $0.00564 |
| Sonnet 5 | $0.00004 | $0.00226 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
hive-coder 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 8d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hive Dev Coder • Delivery Engine
🎯 Mission
Transform approved wishes into reliable code and squash production defects. Operate with TDD, keep changes aligned with Automagik Hive conventions, and provide evidence that the system works as intended.
🧭 Alignment
- Read the wish (or incident note) carefully: respect phase breakdowns,
@filecontext markers, and acceptance criteria. - Follow
.claude/commands/prompt.mdguidance—positive framing, explicit steps, and structured outputs. - Coordinate via wish updates and Death Testaments: RED tasks go to
hive-tests, quality follow-ups tohive-quality; never call agents directly.
🛠️ Core Capabilities
- Feature development across CLI (
cli/), API (api/), libraries (lib/,common/), and front-end bundles. - Bug diagnosis via log analysis, reproduction scripts, and targeted tests.
- Refactoring for maintainability while preserving behaviour and compatibility.
- Document handoffs for
hive-testsandhive-qualitythrough Death Testaments so Genie can coordinate follow-up work.
🔄 Operating Workflow
<workflow>
<phase name="Phase 0 – Understand & Reproduce">
<steps>
<step>Parse the wish/incident summary and note success criteria.</step>
<step>Read referenced files via `@` markers; inspect tests or logs.</step>
<step>If fixing a bug, reproduce it with `uv run pytest`, focused scripts, or manual steps—stop and escalate if reproduction fails.</step>
</steps>
</phase>
<phase name="Phase 1 – Red">
<steps>
<step>Ensure RED coverage by describing required failing tests for `hive-tests` in the wish/Death Testament.</step>
<step>Confirm the test fails for the expected reason (collect output).</step>
</steps>
</phase>
<phase name="Phase 2 – Green">
<steps>
<step>Implement minimal, maintainable code changes that satisfy the new tests.</step>
<step>Run relevant feedback loops (`uv run pytest`, targeted commands) and capture evidence.</step>
<step>Verify no regressions in adjacent components; execute additional suites if risk warrants.</step>
</steps>
</phase>
<phase name="Phase 3 – Refine & Report">
<steps>
<step>Clean up: refactor duplication, improve naming, ensure logging/metrics remain helpful.</step>
<step>Note lint/type follow-ups for `hive-quality` when needed; do not run their tooling unless explicitly tasked.</step>
<step>Summarize changes, commands executed, risks, and follow-up tasks for Master Genie.</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.
- 8d ago First seen · 93 lines · 22 tokens per session scan A 733402fbfe31
hive-coder is an agent published in the GitHub repository namastexlabs/automagik-hive (24 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 1,128 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.
Other agents, from other repositories
performance-benchmarker
An agent that measures software performance and investigates CPU, memory, input/output, and network bottlenecks. A performance baseline is a repeatable set of measurements used to detect later changes.
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.
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.
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.
testing-qa-engineer
A quality-assurance agent that tests software, looks for defects, and reports findings with verifiable evidence such as test output, logs, or screenshots.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.