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/review-for-qualitynpx skills add codenamev/claude_memory --skill review-for-qualitygit clone --depth 1 https://github.com/codenamev/claude_memoryWrote 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/skills/codenamev/claude_memory/review-for-quality)<a href="https://agentmods.dev/skills/codenamev/claude_memory/review-for-quality"><img src="https://agentmods.dev/badge/skills/codenamev/claude_memory/review-for-quality.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.1 | $0.00040 | $0.00970 |
| Opus 5 | $0.00020 | $0.00485 |
| Sonnet 5 | $0.00008 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
review-for-quality 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 6d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Review
Critically review this Ruby codebase for best-practices, idiom use, and overall quality through the eyes of Ruby experts.
Expert Perspectives
Analyze the codebase through these 5 perspectives:
-
Sandi Metz (POODR principles)
- Single Responsibility Principle
- Small, focused methods (< 5 lines ideal)
- Classes with single purpose
- DRY principle
- Clear dependencies
- High test coverage
-
Jeremy Evans (Sequel maintainer)
- Proper Sequel usage patterns (datasets over raw SQL)
- Database performance optimization
- Schema design best practices
- Connection management
- Transaction safety
- Sequel plugins and extensions
-
Kent Beck (TDD, Simple Design)
- Test-first design
- Simple solutions over complex ones
- Revealing intent through naming
- Clear boundaries between components
- Testability without mocks
- Command-Query Separation
-
Avdi Grimm (Confident Ruby)
- Confident code (no defensive nil checks everywhere)
- Tell, don't ask principle
- Null object pattern
- Meaningful return values (not nil)
- Duck typing
- Result objects over exceptions
-
Gary Bernhardt (Boundaries, Fast Tests)
- Functional core, imperative shell
- Fast unit tests (no I/O in logic)
- Clear boundaries between layers
- Separation of I/O and pure logic
- Value objects
- Immutable data structures
Review Process
-
Explore the codebase systematically:
lib/claude_memory/(all subdirectories)- Identify the largest files (> 500 lines)
- Find code duplication patterns
- Check architecture and design patterns
-
Document EVERY issue found with:
- Priority: 🔴 Critical / High / 🟡 Medium / Low
- Specific file:line references
- Which expert's principle is violated
- Concrete improvement suggestions with code examples
- Estimated effort to fix
-
Track progress:
- Compare with previous review date
- Show metrics (lines of code, god objects, etc.)
- Identify what's been fixed since last review
- Highlight new issues that have emerged
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 155 lines · 40 tokens per session scan A fc69d8fbf071
review-for-quality is a skill published in the GitHub repository codenamev/claude_memory (24 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 970 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
contributing
Contribute to RubyLLM - set up the repo, run and record specs, add providers or chat options, work on the Rails integration, and edit docs. Use when fixing a bug, building a feature, writing specs, or changing documentation in the RubyLLM codebase.
new
Create a new project to start development quickly.
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
ruby-patterns
Ruby/Rails: blocks, metaprogramming, ActiveRecord, Sidekiq, RSpec, Sorbet, Hanami. Triggers: Ruby, Rails, ActiveRecord, Sidekiq, RSpec, Gemfile, bundler, Hanami, Sorbet.
ruby-idioms
Ruby rewards expressiveness, convention, and developer happiness. Modern Ruby (3.x) favors pattern matching, Ractor for concurrency, and strict typing via Sorbet/RBS. Idiomatic Ruby = readable, tested, convention-following.
ruby-rules
Ruby coding rules: style, patterns, security, testing. Triggers: .rb, Gemfile, .gemspec, Rails, ActiveRecord, Sidekiq, RSpec, Sorbet, rubocop.