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/sonomirco/agents-and-commandsWrote 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/sonomirco/agents-and-commands/pattern-recognition-specialist)<a href="https://agentmods.dev/agents/sonomirco/agents-and-commands/pattern-recognition-specialist"><img src="https://agentmods.dev/badge/agents/sonomirco/agents-and-commands/pattern-recognition-specialist.svg" alt="Measured on agentmods" 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.00000 | $0.00855 |
| Opus 5 | $0.00000 | $0.00428 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pattern-recognition-specialist — 91% identical, 20 lines differ
What it actually says
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 grep or ast-grep for structural matching
- 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
If you encounter project-specific patterns or conventions (especially from CLAUDE.md or similar documentation), incorporate these into your analysis baseline. Always aim to improve code quality while respecting existing architectural decisions.
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.
- 8d ago First seen · 57 lines · 0 tokens per session scan A 505a5fa202d7
pattern-recognition-specialist is an agent published in the GitHub repository sonomirco/agents-and-commands (12 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 855 tokens. 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-30.
Other agents, from other repositories
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
CocoBrew
CocoBrew lifecycle coordinator. Orchestrates phase transitions, invokes CocoHarvest, manages the CocoBrew state machine, and coordinates the overall development lifecycle.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
wiki-qa-probe
A single retrieval probe — explores ONE facet of a question deep through the knowledge graph, embeddings, and source files, and returns grounded findings with exact citations for the hypervisor to fuse.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
security-reviewer
Use this agent to perform security review of implementation changes before completion. Reviews code modifications for vulnerabilities, insecure patterns, and security best practices. Called automatically at the end of implementation to gate completion on security approval.