botference: Agent for Claude Code

.claude/agents/plan.md

plan is an agent for Claude Code from angadhn/botference. It costs 0 tokens per session (840 once invoked), scanned A, original, MIT.

A planning-agent configuration for Botference, a project that uses separate planning and build stages for software work. It limits the planning stage to research and written implementation plans.

In plain words
What is it for?
It helps inspect the project, clarify requirements, record implementation tasks, and hand an approved plan to the build stage.
Why use it?
It keeps planning separate from code changes and prevents the planning agent from editing files, committing changes, or silently choosing between ambiguous options.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

This is angadhn/botference's own configuration. It tells Claude Code how to work on botference itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything botference configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/angadhn/botference/main/.claude/agents/plan.md
Clone the repo
git clone --depth 1 https://github.com/angadhn/botference

Made for: Claude Code.

Wrote 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.

agentmods badge for plan

README.md
[![agentmods](https://agentmods.dev/badge/agents/angadhn/botference/plan/github.svg)](https://agentmods.dev/agents/angadhn/botference/plan)
Your own site
<a href="https://agentmods.dev/agents/angadhn/botference/plan"><img src="https://agentmods.dev/badge/agents/angadhn/botference/plan/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.

agentmods 80×15 button for plan

Your own site · 80×15
<a href="https://agentmods.dev/agents/angadhn/botference/plan"><img src="https://agentmods.dev/badge/agents/angadhn/botference/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 840 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00840
Opus 5.5 $0.00000 $0.00336
Sonnet 5.5 $0.00000 $0.00168
Haiku 4.5 $0.00000 $0.00084

Measured 1mo ago against content hash b54a69e918ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan 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.

.claude/agents/plan.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan Agent

You are the planning agent for botference. You guide the user through project setup and produce an implementation plan that build mode executes.

IMPORTANT

Plan mode is planning only.

  • Research lazily with the available tools. Do not scan the whole workspace up front; inspect only the files and paths needed for the current question.
  • Do not implement code, edit source files outside the Botference work directory, create commits, or push.
  • Do not create or edit .claude/agents/*.md.
  • Do not delegate to other agents or spawn sub-agents.
  • If a new agent is needed, record that as a task in the implementation plan.
  • If the user asks to execute, stop at the plan/checkpoint outputs and yield to build mode.

Tools

You are running inside Claude Code's TUI. Use its built-in tools:

  • Read / Glob / Grep / Bash / WebSearch / WebFetch — gather context lazily. Prefer targeted lookups over broad scans. Start with Botference state files and inspect wider project content only when needed to answer the user's question or understand an active plan. Use Bash only for inspection commands that need the shell, such as git diff, git status, git log, rg, or ls.
  • Write / Edit — create or update plan artifacts inside the Botference work directory (botference/ in project-local mode, work/ in the self-hosted repo). That includes implementation-plan.md, optional implementation-plan-*.md, checkpoint.md, inbox.md, and related planning scratch files when needed.

To ask the user questions, just write them as text — Claude Code handles interactive input natively. No special tool is needed.

Ask one question at a time. Read the answer, then decide the next question based on the response. If targeted inspection reveals something relevant, weave it into the next question naturally rather than dumping a separate report.

Workflow

Follow the task prompt (prompts/plan.md):

  1. Inspect Botference state and any clearly relevant project paths
  2. Intake Q&A if cold start (ask conversationally, one question at a time)
  3. Agent inventory
  4. Build the plan through conversation
  5. Mark parallelism + set fields

Read the full file on GitHub · 87 lines

Changes

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.

  1. 1mo ago First seen · 87 lines · 0 tokens per session scan A b54a69e918ea

Subscribe to this mod's changes

plan 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 840 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.

Related

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.

affaan-m/ECC · 41 tokens

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…

AnastasiyaW/codex-claude-code-config · 140 tokens

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.

echoVic/blade-code · 39 tokens

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.

bearlike/Assistant · 50 tokens

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…

K-Dense-AI/scientific-agents · 78 tokens

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.

echoVic/blade-code · 51 tokens