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 skills/codenamev/claude_memory/analyzenpx skills add codenamev/claude_memory --skill analyzegit clone --depth 1 https://github.com/codenamev/claude_memoryWhat 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.00030 | $0.01003 |
| Opus 5 | $0.00015 | $0.00502 |
| Sonnet 5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
project-analysis 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 2d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Project Skill
Analyze the current project and store facts about it in long-term memory.
Workflow
- Read key project files to understand the tech stack
- Extract facts about languages, frameworks, tools, conventions
- Store facts using
memory.store_extraction
Files to Read
Read these files (if they exist) to understand the project:
Package/Dependency Files
Gemfile- Ruby dependencies (Rails, RSpec, etc.)package.json- JavaScript/TypeScript dependenciespyproject.tomlorrequirements.txt- Python dependenciesCargo.toml- Rust dependenciesgo.mod- Go dependenciespom.xmlorbuild.gradle- Java dependencies
Configuration Files
README.md- Project overview and setup instructionstsconfig.json- TypeScript configuration.eslintrc*oreslint.config.*- ESLint configuration.prettierrc*- Prettier configuration.rubocop.ymlor.standard.yml- Ruby lintingDockerfile- Container configuration.github/workflows/*.yml- CI/CD configuration
Convention Files
.editorconfig- Editor configurationCLAUDE.mdorAGENTS.md- AI assistant instructions
What to Extract
Look for and store facts about:
| Category | Predicate | Examples |
|---|---|---|
| Languages | uses_language |
Ruby, TypeScript, Python, Go, Rust |
| Frameworks | uses_framework |
Rails, React, Next.js, Django, FastAPI |
| Tools | uses_tool |
RSpec, Jest, ESLint, Prettier, Docker |
| Databases | uses_database |
PostgreSQL, MySQL, Redis, MongoDB |
| Package Manager | uses_package_manager |
Bundler, npm, pnpm, Poetry, Cargo |
| CI/CD | uses_ci |
GitHub Actions, CircleCI, GitLab CI |
| Conventions | has_convention |
EditorConfig, 2-space indentation |
Example Analysis
After reading Gemfile:
source 'https://rubygems.org'
gem 'rails', '~> 7.0'
gem 'pg'
gem 'rspec-rails', group: :test
Store these facts:
{
"entities": [
{"type": "language", "name": "Ruby"},
{"type": "framework", "name": "Rails"},
{"type": "database", "name": "PostgreSQL"},
{"type": "tool", "name": "RSpec"}
],
"facts": [
{
"subject": "repo",
"predicate": "uses_language",
"object": "Ruby",
"quote": "Gemfile present",
"strength": "stated"
},
{
"subject": "repo",
"predicate": "uses_framework",
"object": "Rails",
"quote": "gem 'rails', '~> 7.0'",
"strength": "stated"
},
{
"subject": "repo",
"predicate": "uses_database",
"object": "PostgreSQL",
"quote": "gem 'pg'",
"strength": "stated"
},
{
"subject": "repo",
"predicate": "uses_tool",
"object": "RSpec",
"quote": "gem 'rspec-rails'",
"strength": "stated"
},
{
"subject": "repo",
"predicate": "uses_package_manager",
"object": "Bundler",
"quote": "Gemfile present",
"strength": "stated"
}
]
}
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.
- 2d ago First seen · 127 lines · 30 tokens per session scan A 247b79ad30fd
project-analysis is a skill published in the GitHub repository codenamev/claude_memory (24 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,003 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…