OpenAgentsControl: Command for OpenCode

.opencode/command/test-new-command.md

test-new-command is a command for OpenCode from darrenhinde/OpenAgentsControl. It costs 12 tokens per session (115 once invoked), scanned A, original, MIT.

A test command for checking that new commands are automatically detected and added to the project registry. The registry is the project file that records available components.

In plain words
What is it for?
Use it to check command discovery, registry updates, and the build validation for this process.
Why use it?
It helps verify that the auto-detection and registry-update process is working.

Command for OpenCode

Written for OpenCode: installed under .opencode/.

This is darrenhinde/OpenAgentsControl's own configuration. It tells OpenCode how to work on OpenAgentsControl itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OpenAgentsControl configures →

About the project

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.

darrenhinde/OpenAgentsControl · 4,910 stars · on GitHub

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/darrenhinde/OpenAgentsControl/main/.opencode/command/test-new-command.md
Clone the repo
git clone --depth 1 https://github.com/darrenhinde/OpenAgentsControl

Made for: OpenCode.

Wrote 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.

agentmods badge for test-new-command

README.md
[![agentmods](https://agentmods.dev/badge/commands/darrenhinde/openagentscontrol/test-new-command/github.svg)](https://agentmods.dev/commands/darrenhinde/openagentscontrol/test-new-command)
Your own site
<a href="https://agentmods.dev/commands/darrenhinde/openagentscontrol/test-new-command"><img src="https://agentmods.dev/badge/commands/darrenhinde/openagentscontrol/test-new-command/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.

agentmods 80×15 button for test-new-command

Your own site · 80×15
<a href="https://agentmods.dev/commands/darrenhinde/openagentscontrol/test-new-command"><img src="https://agentmods.dev/badge/commands/darrenhinde/openagentscontrol/test-new-command.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00115
Opus 5.5 $0.00005 $0.00046
Sonnet 5.5 $0.00002 $0.00023
Haiku 4.5 $0.00001 $0.00012

Measured 1mo ago against content hash 6877cc8dc881, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

test-new-command 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.

.opencode/command/test-new-command.md · 27 lines

What it actually says

Test New Command

This is a test command created to verify that the auto-detection system works.

Usage

/test-new-command

Features

  • Auto-detected by the system
  • Automatically added to registry
  • Validates the build system works

Testing

This file should be:

  1. Detected by auto-detect-components.sh
  2. Added to registry.json automatically
  3. Validated by validate-registry.sh
Changes

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.

  1. 1mo ago First seen · 27 lines · 12 tokens per session scan A 6877cc8dc881

Subscribe to this mod's changes

test-new-command is a command published in the GitHub repository darrenhinde/OpenAgentsControl (4,910 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 115 once invoked, about $0.0000 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.