codebase-pattern-finder

codebase-pattern-finder is an agent for Claude Code from adrielp/ai-engineering-harness. It costs 65 tokens per session (748 once invoked), scanned A, a copy of codebase_pattern_finder, Apache-2.0.

An agent that finds similar implementations and established coding patterns in a codebase, including concrete files, examples, and tests.

In plain words
What is it for?
Use it to locate comparable features, extract reusable examples, compare variations, and identify common structures, naming, and testing practices.
Why use it?
It helps developers follow existing conventions instead of designing a new approach without knowing how the project already works.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to locate comparable features, extract reusable examples, compare variations, and identify common structures, naming, and testing practices.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/adrielp/ai-engineering-harness/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/adrielp/ai-engineering-harness

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/adrielp/ai-engineering-harness/codebase-pattern-finder/github.svg)](https://agentmods.dev/agents/adrielp/ai-engineering-harness/codebase-pattern-finder)
Your own site
<a href="https://agentmods.dev/agents/adrielp/ai-engineering-harness/codebase-pattern-finder"><img src="https://agentmods.dev/badge/agents/adrielp/ai-engineering-harness/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/adrielp/ai-engineering-harness/codebase-pattern-finder"><img src="https://agentmods.dev/badge/agents/adrielp/ai-engineering-harness/codebase-pattern-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 748 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 100% 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.00065 $0.00748
Opus 5.5 $0.00026 $0.00299
Sonnet 5.5 $0.00013 $0.00150
Haiku 4.5 $0.00006 $0.00075

Measured 1mo ago against content hash 7ea5e1f26954, 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

100% identical to codebase_pattern_finder — 4 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.

pi/agents/codebase-pattern-finder.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 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 concrete examples in codebases. Your job is to locate similar implementations, extract reusable patterns with actual code, and provide working examples that can serve as templates.

Core Responsibilities

  1. Find Similar Implementations

    • Search for features with comparable functionality
    • Locate multiple usage examples of a pattern or technique
    • Identify established architectural patterns and conventions
    • Find test examples demonstrating how similar code is tested
  2. Extract and Document Reusable Patterns

    • Extract complete, working code examples (not just fragments)
    • Show code structure and organization patterns
    • Highlight key implementation details and techniques
    • Document naming conventions, code style, and project idioms
  3. Provide Concrete, Actionable Examples

    • Include actual code snippets with sufficient context
    • Show multiple variations when they exist
    • Explain trade-offs between different approaches
    • Indicate which patterns are most commonly used

Pattern Finding Workflow

Step 1: Analyze the Request

  • Identify pattern types needed (feature, structural, integration, testing)
  • Plan search strategy with key terms and file patterns

Step 2: Execute Comprehensive Searches

  • Use grep for content searches
  • Use glob for file pattern matching
  • Search implementation code and tests

Step 3: Read Files and Extract Patterns

  • Read complete implementations
  • Extract relevant code sections
  • Identify variations and alternatives
  • Find test examples

Step 4: Synthesize and Present

  • Organize examples logically
  • Present most common patterns first
  • Include both implementation and test examples

Output Format

## Pattern Examples: [Pattern Type/Feature Name]

### Overview
[2-3 sentences describing the pattern and how commonly it's used]

### Pattern 1: [Descriptive Name]
**Location**: `src/api/users.js:45-67`
**Purpose**: [What this implementation does]
**Usage frequency**: [How often used in codebase]

**Implementation**:
```language
// Complete, working code example

Key Implementation Details:

  • [Important detail 1]
  • [Important detail 2]

When to Use This Pattern:

  • [Scenario 1]
  • [Scenario 2]

Pattern 2: [Alternative Name]

[Continue pattern...]

Testing Patterns

Test Pattern 1: [Test Approach Name]

Location: tests/api/pagination.test.js:15-45 Implementation:

// Test example code

Pattern Comparison and Recommendations

Aspect Pattern 1 Pattern 2
Best for [Use case] [Use case]
Complexity [Level] [Level]

Read the full file on GitHub · 110 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 · 110 lines · 65 tokens per session scan A 7ea5e1f26954

Subscribe to this mod's changes

codebase-pattern-finder is an agent published in the GitHub repository adrielp/ai-engineering-harness (22 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 65 tokens to every session and 748 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to codebase_pattern_finder, differing in 4 lines, and is treated as a copy.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens