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/validate-repo.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/validate-repo)<a href="https://agentmods.dev/commands/darrenhinde/openagentscontrol/validate-repo"><img src="https://agentmods.dev/badge/commands/darrenhinde/openagentscontrol/validate-repo/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/validate-repo"><img src="https://agentmods.dev/badge/commands/darrenhinde/openagentscontrol/validate-repo.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.00000 | $0.02029 |
| Opus 5.5 | $0.00000 | $0.00812 |
| Sonnet 5.5 | $0.00000 | $0.00406 |
| Haiku 4.5 | $0.00000 | $0.00203 |
Grade A, and why
validate-repo 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Repository
Comprehensive validation command that checks the entire OpenAgents Control repository for consistency between CLI, documentation, registry, and components.
Usage
/validate-repo
What It Checks
This command performs a comprehensive validation of:
-
Registry Integrity
- JSON syntax validation
- Component definitions completeness
- File path references
- Dependency declarations
-
Component Existence
- All agents exist at specified paths
- All subagents exist at specified paths
- All commands exist at specified paths
- All tools exist at specified paths
- All plugins exist at specified paths
- All context files exist at specified paths
- All config files exist at specified paths
-
Profile Consistency
- Component counts match documentation
- Profile descriptions are accurate
- Dependencies are satisfied
- No duplicate components
-
Documentation Accuracy
- README component counts match registry
- OpenAgent documentation references are valid
- Context file references are correct
- Installation guide is up to date
-
Context File Structure
- All referenced context files exist
- Context file organization is correct
- No orphaned context files
-
Cross-References
- Agent dependencies exist
- Subagent references are valid
- Command references are valid
- Tool dependencies are satisfied
Output
The command generates a detailed report showing:
- ✅ What's correct and validated
- ⚠️ Warnings for potential issues
- ❌ Errors that need fixing
- 📊 Summary statistics
Instructions
You are a validation specialist. Your task is to comprehensively validate the OpenAgents Control repository for consistency and correctness.
Step 1: Validate Registry JSON
- Read and parse
registry.json - Validate JSON syntax
- Check schema structure:
versionfield existsrepositoryfield existscategoriesobject existscomponentsobject exists with all typesprofilesobject existsmetadataobject exists
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 · 348 lines · 0 tokens per session scan A 25bfd5983ba9
validate-repo is a command published in the GitHub repository darrenhinde/OpenAgentsControl (4,910 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,029 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-09-14.
Other commands, from other repositories
guard
Manually run the Hydra security and quality scan on specified files or directories.
investigator
Root-cause debugging specialist that diagnoses issues through systematic investigation before proposing any fix. Trigger on bug, debug, investigate, root cause, incident, post-mortem, or when something is broken.
hw-troubleshoot
A hardware diagnostic command that scans for I²C devices, checks power, and analyzes signal quality. I²C is a short-distance communication bus used by many sensors and chips.
modbus-debug
A Modbus device debugging command. Modbus is a communication protocol commonly used by industrial controllers and other equipment.
mqtt-debug
A command for debugging MQTT, a messaging protocol commonly used by connected devices and services. It covers publishing messages, monitoring subscriptions, and checking connections.
analyze
Deep analysis of specific code or module.