OpenAgents Control is a framework that adds plan-first, approval-based coding workflows to OpenCode, an AI coding framework. Developers and teams use it to make agents follow shared coding patterns, work across several programming languages, and validate changes through testing and review. The catalogue includes its agents, skills, commands, plugin, and hook.
Borrowing it
Nothing to install: this file belongs to darrenhinde/OpenAgentsControl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/darrenhinde/OpenAgentsControl/main/.opencode/command/analyze-patterns.mdgit clone --depth 1 https://github.com/darrenhinde/OpenAgentsControlWrote 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/commands/darrenhinde/openagentscontrol/analyze-patterns)<a href="https://agentmods.dev/commands/darrenhinde/openagentscontrol/analyze-patterns"><img src="https://agentmods.dev/badge/commands/darrenhinde/openagentscontrol/analyze-patterns/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/commands/darrenhinde/openagentscontrol/analyze-patterns"><img src="https://agentmods.dev/badge/commands/darrenhinde/openagentscontrol/analyze-patterns.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.00013 | $0.01342 |
| Opus 5.5 | $0.00005 | $0.00537 |
| Sonnet 5.5 | $0.00003 | $0.00268 |
| Haiku 4.5 | $0.00001 | $0.00134 |
Grade A, and why
analyze-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: analyze-patterns
Description
Analyze codebase for recurring patterns, similar implementations, and refactoring opportunities. Replaces codebase-pattern-analyst subagent functionality with a command-based interface.
Usage
/analyze-patterns [--pattern=<pattern>] [--language=<lang>] [--depth=<level>] [--output=<format>]
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
--pattern |
string | No | Pattern name or regex to search for (e.g., "singleton", "factory", "error-handling") |
--language |
string | No | Filter by language: js, ts, py, go, rust, java, etc. |
--depth |
string | No | Search depth: shallow (current dir) | medium (src/) | deep (entire repo) |
--output |
string | No | Output format: text (default) | json | markdown |
Behavior
Pattern Search
- Searches codebase for pattern matches using regex + semantic analysis
- Identifies similar implementations across files
- Groups results by pattern type + similarity score
- Suggests refactoring opportunities
Analysis Output
- Pattern occurrences with file locations + line numbers
- Similarity metrics (how similar are implementations?)
- Refactoring suggestions (consolidate, extract, standardize)
- Code quality insights (duplication, inconsistency)
Result Format
Pattern Analysis Report
=======================
Pattern: [pattern_name]
Occurrences: [count]
Files: [file_list]
Implementations:
1. [file:line] - [description] (similarity: X%)
2. [file:line] - [description] (similarity: Y%)
...
Refactoring Suggestions:
- [suggestion 1]
- [suggestion 2]
...
Quality Insights:
- [insight 1]
- [insight 2]
...
Examples
Find all error handling patterns
/analyze-patterns --pattern="error-handling" --language=ts
Analyze factory patterns across codebase
/analyze-patterns --pattern="factory" --depth=deep --output=json
Find similar API endpoint implementations
/analyze-patterns --pattern="api-endpoint" --language=js --output=markdown
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 · 222 lines · 13 tokens per session scan A a823c66135d5
analyze-patterns is a command published in the GitHub repository darrenhinde/OpenAgentsControl (4,910 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,342 once invoked, about $0.0001 per session on Opus 5.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-09-14.
Other commands, from other repositories
query
Ask questions about a repository/codebase and get detailed answers with file citations.
critic
Plan critic. Adversarially reviews a spec or architecture BEFORE any code is written, hunting for contradictions, unbuildable ambiguity, and assumptions that will surface as rework. Runs as a gate between design and build. Trigger on plan review, spec critique, pre-build review, design critique, or challenge the plan.
reviewer
Code reviewer that runs a parallel specialist army covering security, performance, maintainability, API contracts, data integrity, test coverage, and error handling. Trigger on code review, review, PR review, pull request, or review army.
Icon Review
Intelligent project and code analysis that automatically selects the most relevant legendary experts across all domains based on your codebase and changes.
Icon Programming Review
Intelligent programming analysis that automatically selects the right legendary programmers for your code and architecture problems.
code-review
Confidence-based code review checklist.