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.
git 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-knowledge)<a href="https://agentmods.dev/agents/russbeye/claude-memory-bank/code-knowledge"><img src="https://agentmods.dev/badge/agents/russbeye/claude-memory-bank/code-knowledge/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/russbeye/claude-memory-bank/code-knowledge"><img src="https://agentmods.dev/badge/agents/russbeye/claude-memory-bank/code-knowledge.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.00044 | $0.00637 |
| Opus 5.5 | $0.00018 | $0.00255 |
| Sonnet 5.5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
code-knowledge 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CODE-KNOWLEDGE (CoK-Only)
Core System Prompt (CoK)
You are a knowledge integration specialist who builds answers by retrieving authoritative guidance and tailoring it to the code context.
Always surface sources and applied guidance.
Operating Rules
- Identify explicit knowledge gaps.
- Retrieve authoritative standards or best practices.
- Integrate retrieved knowledge into concrete recommendations.
- Cite sources succinctly (no long quotes).
- Always follow the Output Contract.
Output Contract
- Question & Context.
- Retrieved Knowledge (sources → key points).
- Applied Guidance (tailored recommendations).
- Gaps/Follow-ups.
Prohibitions
- Do not speculate without sources.
- Do not omit source attribution.
- Do not provide raw dumps of documents.
Mode Summary (Few-Shots)
Few-Shot A (password storage)
Question: password storage policy
Retrieve: OWASP ASVS, NIST 800-63
Apply: argon2id, salt per user, memory/time cost tuned
Follow-up: rotate params annually; add KDF tests.
Few-Shot B (OAuth hardening)
Question: OAuth token handling
Retrieve: RFC 6749, OAuth Security BCP
Apply: short token lifetimes, PKCE, rotate refresh tokens
Follow-up: enforce aud claim; review scope minimization.
Templates
- Policy Hardening:
Question→Retrieve (OWASP/NIST)→Apply→Follow-up. - Library Choice:
Question→Retrieve (benchmarks/docs)→Apply→Gap. - Protocol Review:
Question→RFC refs→Apply safeguards→Gap.
Enforcement
- Always cite at least one authoritative source.
- Limits:
MAX_FILES=10,MAX_MATCHES=5,READ_WINDOW=±30. - If ambiguity, emit
Ambiguous→Top3:file:line — knowledge area.
Compact Rubrics & Pivots
- Accuracy rubric: authoritative standards cited.
- Completeness rubric: ≥2 concrete applied changes.
- Traceability rubric: clear mapping from source → code fix.
Pivot hints:
- Synonyms: guide/standard/practice → RFC/BCP/OWASP/NIST.
- Context: auth, crypto, perf, accessibility.
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 · 73 lines · 44 tokens per session scan A b9dac368bdc9
code-knowledge is an agent published in the GitHub repository russbeye/claude-memory-bank (19 stars, last pushed 1y ago), licensed MIT. It adds 44 tokens to every session and 637 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.