agent-commander: Instructions file for Codex

AGENTS.md

agent-commander AGENTS.md is an instructions file for Codex, OpenCode from cvsloane/agent-commander. It costs 194 tokens per session, scanned A, original, MIT.

A repository instruction file that defines the working contract for agent-commander, including its project overview, development rules, and verification approach.

In plain words
What is it for?
Understanding the repository before editing it, following its scope and safety rules, and choosing the narrowest useful verification command.
Why use it?
It helps an agent keep changes focused and avoid actions such as deployment, deletion, secret rotation, or paid operations unless explicitly requested.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is cvsloane/agent-commander's own configuration. It tells Codex and OpenCode how to work on agent-commander 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 agent-commander configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/cvsloane/dev/agent-command.

Reuse

Borrowing it

Nothing to install: this file belongs to cvsloane/agent-commander. 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/cvsloane/agent-commander/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/cvsloane/agent-commander

Made for: Codex, 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 agent-commander AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cvsloane/agent-commander/agents-md/github.svg)](https://agentmods.dev/instructions/cvsloane/agent-commander/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/cvsloane/agent-commander/agents-md"><img src="https://agentmods.dev/badge/instructions/cvsloane/agent-commander/agents-md/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 agent-commander AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cvsloane/agent-commander/agents-md"><img src="https://agentmods.dev/badge/instructions/cvsloane/agent-commander/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 194 This file is loaded in full into every session.
When invoked 194 The same file — it is already loaded in full.
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.00194 $0.00194
Opus 5.5 $0.00078 $0.00078
Sonnet 5.5 $0.00039 $0.00039
Haiku 4.5 $0.00019 $0.00019

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

Security

Grade A, and why

agent-commander AGENTS.md 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 24 lines

What it actually says

AGENTS.md

Canonical cross-tool instructions for this repo.

Repository Overview

  • Repo: agent-command
  • Location: /home/cvsloane/dev/agent-command
  • Treat this file as the concise always-loaded contract. Put long procedures in repo docs, skills, or SloaneVault.

Working Rules

  • Read the repo before changing code; prefer existing patterns and commands.
  • Keep changes scoped to the task and avoid unrelated refactors.
  • Do not commit, deploy, delete data, rotate secrets, or run paid/bulk operations unless explicitly asked.
  • Preserve user changes and generated work you did not create.
  • Use SloaneVault/qmd for company context and durable documentation instead of pasting large context here.

Verification

  • Run the narrowest command that proves the change works.
  • If commands are unknown, inspect package/config files and document what you ran.
  • Report any verification you could not run and why.
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 · 24 lines · 194 tokens per session scan A 1a8be7a3812c

Subscribe to this mod's changes

agent-commander AGENTS.md is an instructions file published in the GitHub repository cvsloane/agent-commander (5 stars, last pushed 8d ago), licensed MIT. It adds 194 tokens to every session, about $0.0008 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-08-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens