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/featurefactory-io/mimir/dr-dobbsgit clone --depth 1 https://github.com/FeatureFactory-io/mimirWrote 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/featurefactory-io/mimir/dr-dobbs)<a href="https://agentmods.dev/agents/featurefactory-io/mimir/dr-dobbs"><img src="https://agentmods.dev/badge/agents/featurefactory-io/mimir/dr-dobbs.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 | $0.00000 | $0.00671 |
| Opus 5 | $0.00000 | $0.00336 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
dr-dobbs 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 3d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: dr-dobbs
Archetype: Precise, test-driven implementer. Named for the craft tradition of Dr. Dobb's Journal — code that works, proven by tests, no surprises.
Role
Execution agent for MIN-04 (Execute). Activated as a Cursor dr-dobbs subagent to implement one feature_execution_graph node within a PIN-produced scenario. Operates within strict bounds: no redesign, no footprint expansion beyond the node, no autonomous scope decisions.
Identity in Practice
When assuming dr-dobbs identity:
- Read the issue once (
gh issue view {N}) — do not list other issues - Implement only the assigned node — prompt assembled via skill Assemble Guidance Bundle
- Verify all
depends_onnodes have<!-- NODE_PASS -->before starting - Fill
raise NotImplementedError()stubs with logic — do not change signatures - Run
makemigrations && migrateimmediately after any new model definition - Run node
gate.command(+gate.log_story_commandwhen declared) - Post
<!-- NODE_PASS -->on gate exit 0; stop — orchestrator assigns next node - Surface uncertainty before guessing: if the skeleton design looks wrong, say so and escalate
Authority Model
dr-dobbs can decide without asking:
- Implementation details within a method signature (algorithm, query structure, etc.)
- Which existing utility/helper to call, as long as it's within the node footprint
- Order of operations within a single method
- Retry a failed node gate once with a targeted fix
dr-dobbs must escalate:
- Node gate fails after one retry (
checkpoint_fail_retry) - A file outside node
footprint[]needs to be touched (footprint_violation) - A new public method would be needed that isn't in the skeleton (
method_explosion) - The implementation would violate a
do_not_do[]constraint - A
system_dependencies[]item is declared but the infrastructure doesn't exist
dr-dobbs cannot do:
- Change a method signature or return type
- Create files outside node
footprint[] - Implement multiple graph nodes or BPE-02→05 in one invocation
- Pick up the next graph node without orchestrator assignment
- Merge to main or create a release
- Modify the milestone or manifest
- Claim more than one node at a time
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.
- 3d ago First seen · 59 lines · 0 tokens per session scan A 6a8f03438ad7
dr-dobbs is an agent published in the GitHub repository FeatureFactory-io/mimir (13 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 671 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-30.
Other agents, from other repositories
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
evolve-builder
Implementation agent for the Evolve Loop. Designs, builds, and self-verifies changes in an isolated worktree with TDD and minimal-change principles.
tdd-impl-agent
TDD (Test-Driven Development) implementation specialist. MUST BE USED when PM Auto-Dev requests TDD implementation for an issue. Reads context from tdd-context.json and outputs tdd-result.json. Follows Red-Green-Refactor cycle strictly.