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 commands/llcoolblaze/claude-boris/memory-initgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWhat 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.00018 | $0.00841 |
| Opus 5 | $0.00009 | $0.00420 |
| Sonnet 5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
memory-init 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 3d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Memory Bank
Checking Current State...
!ls -la .claude/memory/ 2>/dev/null && echo "Memory Bank exists" || echo "No Memory Bank found"
!pwd
!ls -la
Memory Bank Initialization
1. Create Directory Structure
mkdir -p .claude/memory
mkdir -p .claude/memory/archive
mkdir -p .claude/audit
2. Analyze Project
Gather context from:
- package.json (name, description, scripts)
- README.md (purpose, setup)
- Directory structure
- CLAUDE.md if exists
- Git history
3. Create Memory Files
projectContext.md - Populate from analysis:
# Project Context
## Project Identity
**Name**: [from package.json or directory]
**Purpose**: [from README or infer]
**Repository**: [from git remote]
## Tech Stack
| Layer | Technology |
|-------|------------|
| Language | [detect] |
| Framework | [detect] |
| Testing | [detect] |
## Architecture Overview
[Describe based on directory structure]
## Key Directories
[List main directories and purposes]
activeContext.md - Initialize empty:
# Active Context
## Current Focus
**Working On**: [Fresh start]
**Branch**: [current branch]
**Started**: [today's date]
## Recent Changes
None yet.
## Next Steps
1. Set up development environment
2. Review project structure
3. Identify first task
progress.md - Initialize empty:
# Progress Tracker
## Current Sprint
**Goal**: [To be defined]
## In Progress
| Task | Progress | Notes |
|------|----------|-------|
| Project setup | 100% | Memory Bank initialized |
## Completed
| Task | Completed |
|------|-----------|
| Memory Bank init | [today] |
## Queued
[To be populated]
decisionLog.md - Initialize with template:
# Decision Log
## [Today's Date] - Initialize Memory Bank
### Status
Accepted
### Context
Setting up persistent memory for Claude Code workflow.
### Decision
Use Memory Bank system with structured markdown files.
### Rationale
Prevents context loss between sessions.
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.
- 3d ago First seen · 189 lines · 18 tokens per session scan A ab196b0f44ec
memory-init is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 841 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.