codebase-pattern-finder

codebase-pattern-finder is an agent for coding agents from shahidshabbir-se/my-pi-setup. It costs 76 tokens per session (1,299 once invoked), scanned A, a copy of codebase-pattern-finder, MIT.

A codebase search agent that finds existing implementations, examples, tests, and conventions related to a requested feature.

In plain words
What is it for?
Use it to locate similar features, explain their reusable structure, show code examples, and provide file and line references.
Why use it?
It removes the need to search a large codebase manually when looking for patterns to copy or adapt.

Agent

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.

agentmods
npx agentmods add agents/shahidshabbir-se/my-pi-setup/codebase-pattern-finder
Clone the repo
git clone --depth 1 https://github.com/shahidshabbir-se/my-pi-setup

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/shahidshabbir-se/my-pi-setup/codebase-pattern-finder.svg)](https://agentmods.dev/agents/shahidshabbir-se/my-pi-setup/codebase-pattern-finder)
Your own site
<a href="https://agentmods.dev/agents/shahidshabbir-se/my-pi-setup/codebase-pattern-finder"><img src="https://agentmods.dev/badge/agents/shahidshabbir-se/my-pi-setup/codebase-pattern-finder.svg" alt="Measured on agentmods" 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. Scan, not verified.
Origin 78% 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 $0.00038 $0.00649
Sonnet 5 $0.00015 $0.00260
Haiku 4.5 $0.00008 $0.00130

Measured 5d ago against content hash b8117aba7a58, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, 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 5d 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

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

agent/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. 5d 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 shahidshabbir-se/my-pi-setup (2 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 1,299 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 54 lines, and is treated as a copy.

Related

Other agents, from other repositories

test-engineer

Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…

QwenLM/qwen-code · 119 tokens

ERROR-FIX

A model-mediated harness for reliable agentic software development.

teaql/teaql-agent-kit · 0 tokens

go-expert

Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.

travisjneuman/.claude · 69 tokens

product-analytics-specialist

PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…

travisjneuman/.claude · 80 tokens

architecture-analyst

Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.

travisjneuman/.claude · 36 tokens

architecture-reviewer

Architecture and design review agent — read-only. Evaluates structural decisions, identifies design smells, and flags risks before implementation. Never modifies code. Use before merging architectural changes or after a planner produces a plan.

FlorianBruniaux/claude-code-plugins · 45 tokens