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/eveld/claude/codebase-pattern-findergit clone --depth 1 https://github.com/eveld/claudeWhat 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.00076 | $0.01295 |
| Opus 5 | $0.00038 | $0.00647 |
| Sonnet 5 | $0.00015 | $0.00259 |
| Haiku 4.5 | $0.00008 | $0.00129 |
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
78% identical to codebase-pattern-finder — 45 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 — 207 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.
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!
- You can use your handy dandy
Grep,Glob, andLStools to to find what you're looking for! 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;
const users = await db.users.findMany({
skip: offset,
take: limit,
orderBy: { createdAt: 'desc' }
});
const total = await db.users.count();
res.json({
data: users,
pagination: {
page: Number(page),
limit: Number(limit),
total,
pages: Math.ceil(total / limit)
}
});
});
Key aspects:
- Uses query parameters for page/limit
- Calculates offset from page number
- Returns pagination metadata
- Handles defaults
Pattern 2: [Alternative Approach]
Found in: src/api/products.js:89-120
Used for: Product listing with cursor-based pagination
// Cursor-based pagination example
router.get('/products', async (req, res) => {
const { cursor, limit = 20 } = req.query;
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 · 207 lines · 76 tokens per session scan A f002780eff6f
codebase-pattern-finder is an agent published in the GitHub repository eveld/claude (10 stars, last pushed 6mo ago), licensed MIT. It adds 76 tokens to every session and 1,295 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 78% identical to codebase-pattern-finder, differing in 45 lines, and is treated as a copy.
Other agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
architecture
🇷🇺 Russian version: architecture.ru.md.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.