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.
git clone --depth 1 https://github.com/bl1nk-bot/bl1nk-agents-managerWrote 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.
[](https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/codebase-pattern-finder)<a href="https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/codebase-pattern-finder"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/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.
<a href="https://agentmods.dev/agents/bl1nk-bot/bl1nk-agents-manager/codebase-pattern-finder"><img src="https://agentmods.dev/badge/agents/bl1nk-bot/bl1nk-agents-manager/codebase-pattern-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.01282 |
| Opus 5.5 | $0.00006 | $0.00513 |
| Sonnet 5.5 | $0.00003 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
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.
This is a copy
73% identical to codebase-pattern-finder — 90 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 — 228 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)
}
});
});
```text
**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
```javascript
// 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.
- 1mo ago First seen · 228 lines · 14 tokens per session scan A 1394cd42c992
codebase-pattern-finder is an agent published in the GitHub repository bl1nk-bot/bl1nk-agents-manager (8 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,282 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 73% identical to codebase-pattern-finder, differing in 90 lines, and is treated as a copy.
Other agents, from other repositories
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…
ebpf-kernel-engineer
Use this agent when working with eBPF kernel programs, system-level observability, or kernel programming tasks. Examples include: developing or modifying process.bpf.c and sslsniff.bpf.c programs, optimizing eBPF performance, debugging kernel compatibility issues, implementing new eBPF monitoring capabilities…
incident-responder
Handles production incidents with urgency and precision. Use IMMEDIATELY when production issues occur. Coordinates debugging, implements fixes, and documents post-mortems.
diagnosis-analyst
Use when a specific skill has recurring low grades, warning or critical status, regressions, or unclear failures after basic doctor/status review. Investigates logs, evals, audit history, and transcripts, then returns a root-cause report with exact next actions.
MAF Incident Responder
Use when a deployed MAF 1.3.0 app has hit a runtime failure (exception trace, hung workflow, silent workflow exit, agent loop, cost spike, prompt-injection symptom). Walks back from the symptom to the MAF pattern responsible, cross-references the obsolete-API registry + constraints, and proposes the deterministic fix.…