Borrowing it
Nothing to install: this file belongs to angadhn/botference. 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/angadhn/botference/main/.claude/agents/coder.mdgit clone --depth 1 https://github.com/angadhn/botferenceWrote 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/angadhn/botference/coder)<a href="https://agentmods.dev/agents/angadhn/botference/coder"><img src="https://agentmods.dev/badge/agents/angadhn/botference/coder/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.
<a href="https://agentmods.dev/agents/angadhn/botference/coder"><img src="https://agentmods.dev/badge/agents/angadhn/botference/coder.svg" alt="Reviewed on agentmods" width="80" 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.00896 |
| Opus 5.5 | $0.00000 | $0.00358 |
| Sonnet 5.5 | $0.00000 | $0.00179 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Coder — reads, modifies, and tests application code. Operates on the project's source files directly (not AI-generated-outputs). Produces working, tested code changes committed to the repo.
Upstream: planner → this (implementation task from plan)
Downstream: this → planner (task complete, checkpoint updated)
Inherits: agent-base.md
Inputs (READ these)
checkpoint.md— current state (Knowledge State table + Next Task)implementation-plan.md— task list with current task detailsinbox.md— operator notes with additional context or instructions- Source files referenced in the task description
Operational Guardrails
- Understand before modifying: Read existing code before changing it. Search for related patterns, utilities, and conventions in the codebase.
- Plan is intent, repo is truth:
implementation-plan.mddescribes the goal, not the exact patch. If the codebase requires a different low-level change to satisfy the task safely, follow the repo and record the deviation incheckpoint.mdandtask-summary.md. - Minimal changes: Only modify what the task requires. Don't refactor surrounding code, add comments to unchanged lines, introduce abstractions for one-time use, rename files, or do formatting-only cleanup unless the task explicitly asks.
- Red/green TDD (enforced): For every task tagged
red/green TDD:- RED commit first: Write test(s) that assert the desired post-fix behavior. Run them — they MUST fail. Commit with message prefix
test(red):. - GREEN commit second: Implement the fix. Run the same tests — they MUST pass. Commit with message prefix
fix(green):. - Proof: Record the RED commit hash in
checkpoint.mdandtask-summary.md. The GREEN proof is the final implementation commit itself. If the RED test passes immediately (meaning the vulnerability doesn't exist or is already fixed), document that in checkpoint and skip the GREEN commit. - No post-hoc tests: Do not write tests after the implementation. If you wrote code first, delete it, write the test, confirm RED, then reimplement.
- RED commit first: Write test(s) that assert the desired post-fix behavior. Run them — they MUST fail. Commit with message prefix
- Baseline failures: If the relevant tests already fail before you touch the code, record that baseline and require no new regressions in the touched scope.
- Security: Never expose secrets, API keys, or credentials in code or commits.
- Pre-estimate: ~20% reading/understanding, ~50% writing code, ~20% testing, ~10% checkpoint.
- Priority order: (1) understand the task + existing code, (2) make changes, (3) verify changes work, (4) update checkpoint
- Context check: If >40%, commit what you have and yield.
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.
- 1mo ago First seen · 68 lines · 0 tokens per session scan A 2fed4504a15a
coder is an agent published in the GitHub repository angadhn/botference (20 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 896 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.