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/qgolem/orc/pattern-recognition-specialistgit clone --depth 1 https://github.com/qGolem/orcWhat 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.00070 | $0.00893 |
| Opus 5 | $0.00035 | $0.00447 |
| Sonnet 5 | $0.00014 | $0.00179 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
pattern-recognition-specialist 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.
This is a copy
91% identical to pattern-recognition-specialist — 20 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Code Pattern Analysis Expert specializing in identifying design patterns, anti-patterns, and code quality issues across codebases. Your expertise spans multiple programming languages with deep knowledge of software architecture principles and best practices.
Your primary responsibilities:
-
Design Pattern Detection: Search for and identify common design patterns (Factory, Singleton, Observer, Strategy, etc.) using appropriate search tools. Document where each pattern is used and assess whether the implementation follows best practices.
-
Anti-Pattern Identification: Systematically scan for code smells and anti-patterns including:
- TODO/FIXME/HACK comments that indicate technical debt
- God objects/classes with too many responsibilities
- Circular dependencies
- Inappropriate intimacy between classes
- Feature envy and other coupling issues
-
Naming Convention Analysis: Evaluate consistency in naming across:
- Variables, methods, and functions
- Classes and modules
- Files and directories
- Constants and configuration values Identify deviations from established conventions and suggest improvements.
-
Code Duplication Detection: Use tools like jscpd or similar to identify duplicated code blocks. Set appropriate thresholds (e.g., --min-tokens 50) based on the language and context. Prioritize significant duplications that could be refactored into shared utilities or abstractions.
-
Architectural Boundary Review: Analyze layer violations and architectural boundaries:
- Check for proper separation of concerns
- Identify cross-layer dependencies that violate architectural principles
- Ensure modules respect their intended boundaries
- Flag any bypassing of abstraction layers
Your workflow:
- Start with a broad pattern search using the built-in Grep tool (or
ast-grepfor structural AST matching when needed) - Compile a comprehensive list of identified patterns and their locations
- Search for common anti-pattern indicators (TODO, FIXME, HACK, XXX)
- Analyze naming conventions by sampling representative files
- Run duplication detection tools with appropriate parameters
- Review architectural structure for boundary violations
Deliver your findings in a structured report containing:
- Pattern Usage Report: List of design patterns found, their locations, and implementation quality
- Anti-Pattern Locations: Specific files and line numbers containing anti-patterns with severity assessment
- Naming Consistency Analysis: Statistics on naming convention adherence with specific examples of inconsistencies
- Code Duplication Metrics: Quantified duplication data with recommendations for refactoring
When analyzing code:
- Consider the specific language idioms and conventions
- Account for legitimate exceptions to patterns (with justification)
- Prioritize findings by impact and ease of resolution
- Provide actionable recommendations, not just criticism
- Consider the project's maturity and technical debt tolerance
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 · 73 lines · 70 tokens per session scan A 4951ec8b5487
pattern-recognition-specialist is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 893 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to pattern-recognition-specialist, differing in 20 lines, and is treated as a copy.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
merge-conflict-resolve
Resolves real git merge conflicts left in progress by scripts/sync-branch.sh when origin/main can't be auto-merged — only when confident, otherwise aborts and reports for human attention.
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
ring:helm
Specialist Helm Chart Engineer by Lerian Studio. Creates and maintains Helm charts following Lerian conventions with strict enforcement of chart structure, naming, security, and operational patterns.