codebase-pattern-finder

codebase-pattern-finder is an agent for Claude Code from juicesharp/rpiv-mono. It costs 76 tokens per session (1,299 once invoked), scanned A, a copy of codebase-pattern-finder, MIT.

A code-search helper that finds similar implementations, examples, and tests in an existing codebase. It explains the patterns it finds and points to the relevant files and lines.

In plain words
What is it for?
Use it to locate reusable code patterns, compare implementation approaches, find project conventions, and gather examples for new work.
Why use it?
It reduces the time spent searching for how a project already handles a feature, structure, integration, or test.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Use it to locate reusable code patterns, compare implementation approaches, find project conventions, and gather examples for new work.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/juicesharp/rpiv-mono/codebase-pattern-finder
Install

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.

Clone the repo
git clone --depth 1 https://github.com/juicesharp/rpiv-mono

Made for: Claude Code.

Wrote 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.

agentmods badge for codebase-pattern-finder

README.md
[![agentmods](https://agentmods.dev/badge/agents/juicesharp/rpiv-mono/codebase-pattern-finder/github.svg)](https://agentmods.dev/agents/juicesharp/rpiv-mono/codebase-pattern-finder)
Your own site
<a href="https://agentmods.dev/agents/juicesharp/rpiv-mono/codebase-pattern-finder"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-mono/codebase-pattern-finder/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for codebase-pattern-finder

Your own site · 80×15
<a href="https://agentmods.dev/agents/juicesharp/rpiv-mono/codebase-pattern-finder"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-mono/codebase-pattern-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 81% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.01299
Opus 5.5 $0.00030 $0.00520
Sonnet 5.5 $0.00015 $0.00260
Haiku 4.5 $0.00008 $0.00130

Measured 1mo ago against content hash b8117aba7a58, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

Origin

This is a copy

81% identical to codebase-pattern-finder — 56 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.

packages/rpiv-pi/agents/codebase-pattern-finder.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 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

  1. Find Similar Implementations

    • Search for comparable features
    • Locate usage examples
    • Identify established patterns
    • Find test examples
  2. Extract Reusable Patterns

    • Show code structure
    • Highlight key patterns
    • Note conventions used
    • Include test patterns
  3. 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, and LS tools 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;

Read the full file on GitHub · 208 lines

Changes

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.

  1. 1mo ago First seen · 208 lines · 76 tokens per session scan A b8117aba7a58

Subscribe to this mod's changes

codebase-pattern-finder is an agent published in the GitHub repository juicesharp/rpiv-mono (901 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 1,299 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to codebase-pattern-finder, differing in 56 lines, and is treated as a copy.

Related

Other agents, from other repositories

debugger

Diagnoses and fixes failed modules using root-cause analysis, not guessing.

TT-Wang/forge · 17 tokens

loom-advisor

Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.

cosmix/loom · 53 tokens

debugger

Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.

bostonaholic/rpikit · 28 tokens

evolve-retrospective

Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.

mickeyyaya/evolve-loop · 51 tokens

type-reconstructor

Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…

marcosd4h/DeepExtractRuntime · 63 tokens

runtime-observer

Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.

richfrem/agent-plugins-skills · 56 tokens