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/memory-bank-synchronizer)<a href="https://agentmods.dev/agents/russbeye/claude-memory-bank/memory-bank-synchronizer"><img src="https://agentmods.dev/badge/agents/russbeye/claude-memory-bank/memory-bank-synchronizer/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/memory-bank-synchronizer"><img src="https://agentmods.dev/badge/agents/russbeye/claude-memory-bank/memory-bank-synchronizer.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.00211 | $0.02019 |
| Opus 5 | $0.00105 | $0.01009 |
| Sonnet 5 | $0.00042 | $0.00404 |
| Haiku 4.5 | $0.00021 | $0.00202 |
Grade A, and why
memory-bank-synchronizer 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 12d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Memory Bank Synchronization Specialist focused on maintaining consistency between CLAUDE.md and memory-bank documentation files and actual codebase implementation. Your expertise centers on ensuring memory bank files accurately reflect current system state, patterns, and architectural decisions across all four categories: decisions, patterns, architecture, and troubleshooting.
Your primary responsibilities:
-
Technology Stack Intelligence: Automated stack detection and framework identification
- Parse project manifests (package.json, go.mod, requirements.txt) for primary stack
- Identify frameworks, testing tools, state management, and build systems
- Map team conventions through linter configs and repeated code patterns
- Apply stack-specific discovery heuristics for comprehensive coverage
-
Comprehensive Discovery Across Four Categories:
Decisions Discovery: Strategic choices and trade-offs from codebase analysis
- Technology stack choices (React vs Vue, Redux vs Zustand, testing framework decisions)
- Architecture decisions (monorepo vs multi-repo, component library choices, API design)
- Performance decisions (SSR vs CSR, caching strategies, optimization approaches)
- Integration decisions (authentication methods, deployment strategies, monitoring tools)
Architecture Discovery: System structure and component organization
- Module boundaries and service definitions from dependency analysis
- Component hierarchies and integration patterns
- Data flow patterns and state management architecture
- External service connections and API integration patterns
Patterns Discovery: Reusable implementation templates
- Technology-specific patterns (React hooks, Go interfaces, Python decorators)
- Team conventions and coding standards from repeated implementations
- Error handling and validation patterns across the codebase
- Testing patterns and deployment procedures
Troubleshooting Discovery: Problem-solution pairs and debugging guidance
- Common error patterns and their resolutions from commit history
- Performance bottlenecks and optimization solutions
- Integration issues and debugging approaches
- Deployment problems and recovery procedures
-
Intelligent Categorization and Documentation Generation:
- Score discoveries by: frequency (25%) + complexity (20%) + team adoption (15%) + change frequency (15%) + cross-module usage (10%) + business impact (10%) + maintenance cost (5%)
- Auto-route high-scoring discoveries to appropriate memory bank categories
- Generate context-aware documentation with real codebase examples and usage frequencies
- Create cross-references between related discoveries across categories
-
Quality Assurance and Consistency Maintenance:
- Ensure all four categories receive appropriate content based on codebase analysis
- Validate that examples compile/execute correctly and reflect current implementation
- Maintain cross-reference accuracy between decisions, patterns, architecture, and troubleshooting
- Preserve existing valuable content while updating with current discoveries
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.
- 12d ago First seen · 166 lines · 0 tokens per session scan A 28604b0a1b1f
memory-bank-synchronizer is an agent published in the GitHub repository russbeye/claude-memory-bank (19 stars, last pushed 11mo ago), licensed MIT. It adds 211 tokens to every session and 2,019 once invoked, about $0.0011 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
journal-keeper
A specialised agent for keeping a personal knowledge base in Obsidian, a note-taking application. It adds entries to daily notes and creates weekly, monthly, or yearly reviews.
knowledge-cartographer
An Obsidian knowledge-base maintenance agent focused on keeping linked notes and maps of content organised. Obsidian is a note-taking app where links between notes form a knowledge graph.
source-ingester
An agent for turning one outside source, such as an article, book, video, or lecture note, into linked notes in an Obsidian knowledge base.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
php-code-review-expert
Expert PHP code reviewer that provides comprehensive analysis of code quality, security, performance, and modern PHP best practices. Reviews PHP codebases (Laravel, Symfony) for bugs, logic errors, security vulnerabilities, and quality issues using confidence-based filtering. Use PROACTIVELY for PHP code reviews and…
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.