What is command_line_reporter AGENTS.md?

A set of repository instructions for developing the Ruby command_line_reporter package. It describes the project layout, coding conventions, commands, and tests.

Use it when editing the gem, running its RSpec tests, checking Ruby style with RuboCop, monitoring tests during changes, or building the package.

It gives a coding agent the project-specific rules needed to make consistent changes and check that they work.

How wbailey/command_line_reporter configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to wbailey/command_line_reporter. 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/wbailey/command_line_reporter/master/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/wbailey/command_line_reporter

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/wbailey/command_line_reporter/agents-md/github.svg)](https://agentmods.dev/instructions/wbailey/command_line_reporter/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/wbailey/command_line_reporter/agents-md"><img src="https://agentmods.dev/badge/instructions/wbailey/command_line_reporter/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/wbailey/command_line_reporter/agents-md"><img src="https://agentmods.dev/badge/instructions/wbailey/command_line_reporter/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 480 This file is loaded in full into every session.

When invoked 480 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.00480	$0.00480
Opus 5.5	$0.00192	$0.00192
Sonnet 5.5	$0.00096	$0.00096
Haiku 4.5	$0.00048	$0.00048

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

Security

Grade A, and why

command_line_reporter 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 2mo 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 · 41 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

This is a Ruby gem. The main entry point is lib/command_line_reporter.rb, with core classes under lib/command_line_reporter/ (tables, rows, columns, options validation) and formatter implementations in lib/command_line_reporter/formatter/. RSpec specs live in spec/, with shared helpers and matchers under spec/support/. Packaging and tooling files include command_line_reporter.gemspec, Gemfile, Rakefile, and Guardfile.

Build, Test, and Development Commands

Use Ruby 3.4.8 (see .ruby-version) and bundle install before running commands.
bundle install installs development and runtime dependencies.
bundle exec rspec runs the full test suite.
bundle exec guard runs specs on file changes (per Guardfile).
bundle exec rubocop checks style against .rubocop.yml.
bundle exec rake build builds the gem package (Bundler gem tasks).

Coding Style & Naming Conventions

Ruby with 2-space indentation.
Use standard Ruby naming: snake_case for methods/variables and CamelCase for classes/modules.
Follow .rubocop.yml (line length limits are disabled; documentation is not required by default).
Keep formatter-specific code in lib/command_line_reporter/formatter/ and public API methods within the CommandLineReporter module.

Testing Guidelines

RSpec is the test framework; files use the *_spec.rb naming pattern.
Load shared helpers via spec/spec_helper.rb.
Add or update specs close to the feature they cover (for example, lib/command_line_reporter/table.rb → spec/table_spec.rb).
No explicit coverage threshold is enforced.

Commit & Pull Request Guidelines

Commit messages in history are short and descriptive (often lowercase, e.g., "version bump", "updated documentation"). Keep summaries concise and focused.
Prefer small, single-purpose commits that describe intent or affected area.
PRs should include: a brief problem statement, summary of changes, tests run, and any behavior changes. Link related issues when applicable.

Read the full file on GitHub · 41 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.

2mo ago First seen · 41 lines · 480 tokens per session scan A 9c23b196b3ee

Subscribe to this mod's changes

command_line_reporter AGENTS.md is an instructions file published in the GitHub repository wbailey/command_line_reporter (426 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 480 tokens to every session, about $0.0019 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-30.

command_line_reporter AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
command_line_reporter AGENTS.mdwbailey/command_line_reporter	Instructions file	426	6mo ago	Apache-2.0	A	480	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	today	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

command_line_reporter: Instructions file for Codex