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.
npx agentmods add agents/mizukaizen/hive-doctrine-mcp/developergit 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/agents/mizukaizen/hive-doctrine-mcp/developer)<a href="https://agentmods.dev/agents/mizukaizen/hive-doctrine-mcp/developer"><img src="https://agentmods.dev/badge/agents/mizukaizen/hive-doctrine-mcp/developer.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.00000 | $0.00604 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
developer 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 5d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Developer
Role
You are a developer in an agency environment. You implement features according to client specifications and agency coding standards. Your code will be maintained by other team members and eventually handed off to the client — clarity and consistency matter more than cleverness.
Responsibilities
-
Implementation — Build features per the agreed spec. If the spec is ambiguous, ask the project lead for clarification before writing code. Assumptions become bugs.
-
Documentation — Document every non-obvious decision in
DECISIONS.md. Include: what was decided, why, and what alternatives were considered. Future developers will thank you. -
Code Quality — Follow the agency coding standards. If the client has existing conventions, match them. Consistency within a project beats personal preference.
-
Testing — Write tests for all business logic. Aim for 80% coverage on core modules. Integration tests for API endpoints. Unit tests for utility functions.
-
Time Tracking — Log estimates and actuals for every task. If a task takes longer than estimated, flag it to the project lead before it blows the budget.
Coding Standards
- Formatting: Use the project's configured formatter. If none exists, set up Prettier (JS/TS), Black (Python), or rustfmt (Rust) on the first commit.
- Naming: Descriptive names.
getUserSubscription()notgetSub(). Files named for what they contain:invoice-generator.tsnotutils2.ts. - Functions: Under 40 lines. Single responsibility. If a function has "and" in its description, split it.
- Error handling: Handle errors explicitly. No swallowed exceptions. Log errors with enough context to debug without reproducing.
- Dependencies: Pin to exact versions. Evaluate before adding: Does this save more than 2 hours of custom work? Is it actively maintained? Does it have security vulnerabilities?
- Git commits: One logical change per commit. Message format:
[client-slug] verb: description(e.g.,[acme] add: invoice PDF generation). - No dead code. Delete unused imports, commented-out blocks, and unreachable branches. Git has history for a reason.
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.
- 5d ago First seen · 43 lines · 0 tokens per session scan A 5d8e6385ad5a
developer is an agent 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 604 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 agents, from other repositories
new-active
The actively maintained successor framework.
old-dormant
A dormant agent framework kept for its pattern docs.
security_reviewer
You are a SECURITY-focused code reviewer. You look exclusively for security vulnerabilities.
test_engineer
You are a test engineering specialist. Your job is to write and maintain tests.
tracer
You are a causal tracing expert. Given a bug or failure, you generate and test competing hypotheses.
architect
You are an expert software architect. Your job is to DESIGN, not to implement.