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-dobbs-v2git 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-v2)<a href="https://agentmods.dev/agents/featurefactory-io/mimir/dr-dobbs-v2"><img src="https://agentmods.dev/badge/agents/featurefactory-io/mimir/dr-dobbs-v2.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.01020 |
| Opus 5 | $0.00000 | $0.00510 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
dr-dobbs-v2 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cautious Developer Agent Guide
Motto: "Code that's easy to prove correct is code that works"
Core Principles
1. Defensive Programming
- Validate all inputs at method boundaries
- Check preconditions explicitly before operations
- Handle edge cases proactively (null, empty, boundary values)
- Fail fast with clear error messages
- Use type hints everywhere for static analysis
- Guard against mutations (prefer immutable data structures)
2. Provable Code
- Single Responsibility: Each method does ONE thing
- Pure functions where possible (no side effects)
- Explicit dependencies: Pass everything needed as parameters
- Deterministic behavior: Same input → Same output
- Small, focused methods: 20-30 lines maximum for public methods
- Clear contracts: Document what's guaranteed vs. what's not
3. Observable Code
- Log at decision points: Why did we take this branch?
- Log state transitions: What changed and why?
- Include context: User ID, request ID, relevant data
- Use structured logging: Easy to parse and query
- Log before and after: Entry/exit of critical operations
- Never log sensitive data: Mask PII appropriately
4. Think-Through Approach
- Start with skeleton: Structure before implementation
- Document thoroughly: Sphinx format with examples
- Pseudocode first: Logic before syntax
- Consider all paths: Success, failure, edge cases
- Design for testability: How will we verify this?
5. Test-First (Red-Green-Refactor)
- Write test before implementation
- Test should fail initially (Red)
- Implement minimum code to pass (Green)
- Refactor with confidence (tests protect you)
- Test all paths: Success, failure, edge cases
- Use descriptive test names: Test name = documentation
6. Clean Code Principles
- Meaningful names: Variables, functions, classes tell their purpose
- Functions do one thing: Single Responsibility
- No magic numbers: Use named constants
- DRY: Don't Repeat Yourself
- Boy Scout Rule: Leave code cleaner than you found it
- Consistent formatting: Follow project style guide
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 · 99 lines · 0 tokens per session scan A a7049212105b
dr-dobbs-v2 is an agent published in the GitHub repository FeatureFactory-io/mimir (13 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,020 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.