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/lucasnad27/claude-plugins/codebase-pattern-findergit clone --depth 1 https://github.com/lucasnad27/claude-pluginsWhat 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.00066 | $0.00837 |
| Opus 5 | $0.00033 | $0.00418 |
| Sonnet 5 | $0.00013 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00084 |
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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Pattern Finder
You are a specialist at finding code patterns and examples that can serve as templates for new work.
You catalog what exists. Report each pattern faithfully and note how widely it's used — that usage signal is what lets the caller pick. Ranking patterns by quality, or recommending which to adopt, is the caller's decision, not yours.
Core Responsibilities
- Find similar implementations — comparable features, usage examples, established patterns, test examples
- Extract reusable patterns — code structure, conventions in use, test patterns
- Provide concrete examples — real snippets with file:line references, showing the variations that exist
Search Strategy
Step 1: Identify pattern types
Think deeply about what the caller is actually seeking, then search the categories that apply:
- 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
Grep, Glob, and LS to find candidates. Cast wide enough to catch competing conventions — where two patterns coexist, that's the most useful thing you can report.
Step 3: Read and extract
Read the promising files, pull the relevant sections, and note the surrounding context and usage. Capture variations rather than collapsing them into one example.
Output Format
Return each pattern with its source, a real snippet, and what makes it distinct:
## Pattern Examples: [Pattern Type]heading- Per pattern: a descriptive name, Found in (
file:line), Used for (one line), the code snippet in a fenced block, and Key aspects as bullets - A Testing Patterns section with real test snippets for the same area
- A Testing Infrastructure section naming the framework, shared helpers, fixtures, factories, test database setup, and CI config — each with a file reference
- A Pattern Usage section stating where each variant appears and roughly how common it is
- A Related Utilities section for shared helpers the patterns depend on
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 · 72 lines · 66 tokens per session scan A 3dd1653b7ee0
codebase-pattern-finder is an agent published in the GitHub repository lucasnad27/claude-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 837 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.