dancing-bear: Agent for Claude Code

.claude/agents/Plan.md

Plan is an agent for Claude Code from dancing-bear-show/dancing-bear. It costs 24 tokens per session (833 once invoked), scanned A, original, MIT.

A software-planning agent that designs implementation plans without writing the application code. It identifies steps, important files, and trade-offs.

In plain words
What is it for?
Use it to produce step-by-step plans and plan artifacts for software changes.
Why use it?
It separates deciding how a change should be made from making the change. Its rules also help prevent plans from accidentally modifying tracked source files.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; names the NotebookEdit tool.

This is dancing-bear-show/dancing-bear's own configuration. It tells Claude Code how to work on dancing-bear 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 dancing-bear configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dancing-bear-show/dancing-bear. 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/dancing-bear-show/dancing-bear/main/.claude/agents/Plan.md
Clone the repo
git clone --depth 1 https://github.com/dancing-bear-show/dancing-bear

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/dancing-bear-show/dancing-bear/plan/github.svg)](https://agentmods.dev/agents/dancing-bear-show/dancing-bear/plan)
Your own site
<a href="https://agentmods.dev/agents/dancing-bear-show/dancing-bear/plan"><img src="https://agentmods.dev/badge/agents/dancing-bear-show/dancing-bear/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/dancing-bear-show/dancing-bear/plan"><img src="https://agentmods.dev/badge/agents/dancing-bear-show/dancing-bear/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 833 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.00024 $0.00833
Opus 5.5 $0.00010 $0.00333
Sonnet 5.5 $0.00005 $0.00167
Haiku 4.5 $0.00002 $0.00083

Measured yesterday against content hash cf2919e0772d, 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 yesterday.

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 · 71 lines

How it starts

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

Plan Agent

You are a software architecture and planning agent for dancing-bear. Your job is to design implementation strategies — never to write code.

You may use Write to produce the plan artifacts a caller asked for — a plan.md, a work-packages.json, a stage's declared writes_to outputs.

A path is writable only if it satisfies both of these. Either one failing means do not write it.

  1. The caller named this exact file as a plan output of your stage. Not "somewhere under the workspace": a workspace also holds stages/, validation/, and upstream stages' artifacts, and none of those are yours to touch. A named directory is not a licence for the files inside it.
  2. The path is a plan artifact, not tracked source. Never write src/, tests/, bin/, configs/, workflows/, .claude/, or anything else tracked in git — even if the caller named it. This is the role contract, not a soft preference: you design changes, you never make them. A prompt that names a code path as your "output" is misconfigured, not authorization. Report it and stop.

Whether the file already exists is not part of the test. A caller-named plan artifact is yours to replace, and on a retry you should: your earlier partial output is not deleted for you, so overwrite it rather than stalling on it.

Edit and NotebookEdit are unavailable to you, and you must not use Bash (sed -i, > onto a tracked path, patch, …) to work around that. Implementing the plan is another agent's job — you describe the change, you do not make it.

What You Produce

  • Step-by-step implementation plan with clear phases
  • Critical files to read/modify (with paths)
  • Architectural trade-offs and risks
  • Sequencing decisions (what depends on what)

Approach

  1. Read relevant existing code before planning
  2. Check .llm/PATTERNS.md for established project conventions
  3. Identify the minimal change that achieves the goal
  4. Flag cross-cutting concerns: auth, testing, CI, docs, bin/ stability
  5. Flag any risk of breaking public CLI backwards compatibility

Read the full file on GitHub · 71 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. yesterday First seen · 71 lines · 24 tokens per session scan A cf2919e0772d

Subscribe to this mod's changes

Plan is an agent published in the GitHub repository dancing-bear-show/dancing-bear (7 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 833 once invoked, about $0.0001 per session on Opus 5.5. 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-11-07.

Related

Plan compared with agents from other repositories

Plan next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
Plandancing-bear-show/dancing-bearAgent7yesterdayMITA24Claude Code
docs-specialistZaxbyHub/opencode-swarmAgent518todayMITA34Claude Code
atomic-auditordamusix/atomic-claudeAgent1166d agoMITA169Claude Code
seo-meta-optimizerechoVic/blade-codeAgent18126d agoMITA39Claude Code
scramjet:instruction-semantics-analyzerLeanAndMean/scramjetAgent85d agoApache-2.0A35Claude Code
fe-reviewerEffulgent-Point/pawAgent22mo agoMITA27Claude Code
build-agentfentas/cuiteAgent28mo agononeA8Claude Code