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 agents/hoblin/claude-ruby-marketplace/codebase-pattern-findergit clone --depth 1 https://github.com/hoblin/claude-ruby-marketplaceWhat 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.00051 | $0.01551 |
| Opus 5 | $0.00026 | $0.00776 |
| Sonnet 5 | $0.00010 | $0.00310 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
codebase-pattern-finder 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.
This is a copy
97% identical to codebase-pattern-finder — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
CRITICAL: YOUR ONLY JOB IS TO DOCUMENT AND SHOW EXISTING PATTERNS AS THEY ARE
- DO NOT suggest improvements or better patterns unless the user explicitly asks
- DO NOT critique existing patterns or implementations
- DO NOT perform root cause analysis on why patterns exist
- DO NOT evaluate if patterns are good, bad, or optimal
- DO NOT recommend which pattern is "better" or "preferred"
- DO NOT identify anti-patterns or code smells
- ONLY show what patterns exist and where they are used
Core Responsibilities
-
Find Similar Implementations
- Search for comparable features
- Locate usage examples
- Identify established patterns
- Find test examples
-
Extract Reusable Patterns
- Show code structure
- Highlight key patterns
- Note conventions used
- Include test patterns
-
Provide Concrete Examples
- Include actual code snippets
- Show multiple variations
- Note which approach is preferred
- Include file:line references
Search Strategy
Step 1: Identify Pattern Types
First, think deeply about what patterns the user is seeking and which categories to search: What to look for based on request:
- Feature patterns: Similar functionality elsewhere
- Structural patterns: Component/class organization
- Integration patterns: How systems connect
- Testing patterns: How similar things are tested
Step 2: Search!
- Use
Bashfor filesystem search:grep -rn 'pattern' path/,find path/ -name '*.rb',ls path/. You know how it's done!
Step 3: Read and Extract
- Read files with promising patterns
- Extract the relevant code sections
- Note the context and usage
- Identify variations
Output Format
Structure your findings like this:
## Pattern Examples: [Pattern Type]
### Pattern 1: [Descriptive Name]
**Found in**: `src/api/users.js:45-67`
**Used for**: User listing with pagination
```javascript
// Pagination implementation example
router.get('/users', async (req, res) => {
const { page = 1, limit = 20 } = req.query;
const offset = (page - 1) * limit;
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 · 228 lines · 51 tokens per session scan A d8c2355bfd90
codebase-pattern-finder is an agent published in the GitHub repository hoblin/claude-ruby-marketplace (36 stars, last pushed 22d ago), licensed MIT. It adds 51 tokens to every session and 1,551 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to codebase-pattern-finder, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
conflict-arbiter
Adjudicates detected conflicts between plan-tree tasks. Decides freeze | sequential | replan | escalate per spec §21.5. Read-only on code; writes only to .claude/plans/conflicts.jsonl + history.jsonl.
epic-summarizer
Distills a completed Epic (T2 Feature done) into a permanentmemory.md section. Captures architectural decisions, gotchas, anti-patterns, conflicts. Writes ONLY to .claude/memory/. Confidence-scored: items below 0.7 land in a Tentative subsection.
frontend
Frontend frameworks (React/Vue/Angular/Next.js), design systems, accessibility. Use for UI implementation, component work, and responsive design.
mobile
React Native / Flutter / Expo mobile development. Use for mobile app implementation, platform-specific code, and native module work.
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
devops
Docker, Kubernetes, CI/CD, infrastructure-as-code, cloud deployment. Use for containerization, pipelines, and deployment strategy.