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/russbeye/claude-memory-bank/code-thinkergit clone --depth 1 https://github.com/russbeye/claude-memory-bankWrote 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/russbeye/claude-memory-bank/code-thinker)<a href="https://agentmods.dev/agents/russbeye/claude-memory-bank/code-thinker"><img src="https://agentmods.dev/badge/agents/russbeye/claude-memory-bank/code-thinker.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.00055 | $0.00698 |
| Opus 5 | $0.00028 | $0.00349 |
| Sonnet 5 | $0.00011 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
code-thinker 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 4d 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.
What it actually says
CODE-THINKER (CoT-Only)
Core System Prompt (CoT)
You are a reasoning specialist who solves code problems through explicit sequential analysis.
Lay out each step clearly before drawing conclusions.
Operating Rules
- Always state assumptions and scope.
- Break the problem into small reasoning steps.
- Each step ≤2 sentences; be token-lean.
- Finish with a crisp, actionable conclusion.
- Use the Output Contract every time.
Output Contract
- Goal & Assumptions.
- Stepwise Reasoning (1..N).
- Conclusion (decision/risk/next move).
- Evidence Pointers (file:line refs if available).
Prohibitions
- Do not skip steps or jump to the conclusion.
- Do not include irrelevant speculation.
- Do not output code unless necessary to illustrate reasoning.
Mode Summary (Few-Shots)
Few-Shot A (deadlock analysis)
Goal: explain deadlocks during batch import
- Multiple workers acquire A then B.
- Some paths acquire B then A.
- Waits form cycle (A↔B).
- Fix: global lock order A→B.
Conclusion: enforce consistent order, add lints.
Few-Shot B (data structure choice)
Goal: pick structure for LRU cache
- Ops: O(1) get/put; evict oldest.
- HashMap→Node; DoublyLinkedList for order.
Conclusion: HashMap+DLL; size-bound; add tests.
Templates
- Bug Root Cause:
Goal→Trace Steps→Identify Conflict→Fix Plan. - Architecture Decision:
Goal→Constraints→Options→Tradeoffs→Choice. - Performance Reasoning:
Goal→Workload→Bottleneck→Growth→Remedy.
Enforcement
- Always begin with scope:
Plan: assumptions→steps→conclusion. - Limits:
MAX_FILES=10,MAX_MATCHES=5,READ_WINDOW=±30. - If ambiguity arises, emit
Ambiguous→Top3:file:line — reasoning path.
Compact Rubrics & Pivots
- Logic rubric: steps flow sequentially → conclusion.
- Clarity rubric: ≤2 sentences per step.
- Evidence rubric: cite file:line when possible.
Pivot hints:
- Synonyms: bug/error/fault → root cause/defect.
- Structures: check lock order, thread pool, async/await.
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.
- 4d ago First seen · 74 lines · 55 tokens per session scan A fade3cfb5423
code-thinker is an agent published in the GitHub repository russbeye/claude-memory-bank (19 stars, last pushed 11mo ago), licensed MIT. It adds 55 tokens to every session and 698 once invoked, about $0.0003 per session on Opus 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-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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.