What is cli AGENTS.md?

Project instructions for developing a terminal-based coding assistant called TJ Coder. They define how to work on the codebase, including authorization, testing, and use of its command-line tool.

Use them when working inside the TJ Coder repository. They cover development tasks, terminal testing, limited hardware considerations, and the project’s open-source release goals.

They give contributors consistent rules for making changes and testing the assistant. The instructions emphasize using the coder command instead of relying only on unit tests.

How tjcoder-labs/cli configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to tjcoder-labs/cli. 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/tjcoder-labs/cli/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/tjcoder-labs/cli

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/tjcoder-labs/cli/agents-md/github.svg)](https://agentmods.dev/instructions/tjcoder-labs/cli/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/tjcoder-labs/cli/agents-md"><img src="https://agentmods.dev/badge/instructions/tjcoder-labs/cli/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/tjcoder-labs/cli/agents-md"><img src="https://agentmods.dev/badge/instructions/tjcoder-labs/cli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,269 This file is loaded in full into every session.

When invoked 1,269 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.

Model	Per session	Once invoked
Fable 5.1	$0.01269	$0.01269
Opus 5.5	$0.00508	$0.00508
Sonnet 5.5	$0.00254	$0.00254
Haiku 4.5	$0.00127	$0.00127

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

Security

Grade A, and why

cli 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 5d 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.

AGENTS.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coder CLI — Development Guide

⚠️ REQUIRED: Release notes on every change

Every commit that bumps package.json's version MUST add or update the matching release-notes entry in the same commit. go test ./... fails otherwise.

Source of truth: release-notes/releases.json — one file, newest entry first. Format: release-notes/schema.json (JSON Schema).
Entry: version (semver, no v, equal to package.json), date (YYYY-MM-DD, America/Denver), title, summary, and changes grouped by added, changed, deprecated, removed, fixed, security. Each item has text (one plain-language line for users) and optional details, commands (slash commands touched, e.g. "/add"), breaking: true, highlight: true. Optional per entry: covers_from (first version of a batch), min_upgrade_from, requires_restart, notes (known limits).
New version: add an entry at the top. Bumping again before a release? Change the top entry's version and set covers_from to the earlier version.
Regenerate the changelog: go run ./cmd/releasenotes (or make release-notes) rewrites CHANGELOG.md. Never edit CHANGELOG.md by hand. go run ./cmd/releasenotes -check verifies it.
Enforced by: go test ./internal/releasenotes (enforce_test.go). It checks that package.json's version is the newest entry, that entries are sorted, unique and valid against the schema, that schema.json matches the Go types, and that CHANGELOG.md is current.
Machine-readable on purpose: the update system will read this file, both the copy embedded in the binary and the copy on main, to show "what's new". Keep it valid JSON. Make only additive schema changes: never rename, remove or retype a field or category. When you add one, update schema.json, the Go types in internal/releasenotes, and bump schema_version.

This file guides agents and contributors working on the Coder CLI codebase.

Read the full file on GitHub · 73 lines

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.

5d ago Changed · +18 lines · +655 tokens per session ff704377ef6a
1mo ago Changed · -117 lines · -2,294 tokens per session 17eaef3d1dff
2mo ago First seen · 172 lines · 2,908 tokens per session scan A e09d36271967

Subscribe to this mod's changes

cli AGENTS.md is an instructions file published in the GitHub repository tjcoder-labs/cli (10 stars, last pushed today), licensed MIT. It adds 1,269 tokens to every session, about $0.0051 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.

cli AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cli AGENTS.mdtjcoder-labs/cli	Instructions file	10	today	MIT	A	1,269	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

cli: Instructions file for Codex