Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/wbailey/command_line_reporter/agents-mdgit clone --depth 1 https://github.com/wbailey/command_line_reporterWhat 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 | $0.00480 | $0.00480 |
| Opus 5 | $0.00240 | $0.00240 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
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 2d 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 — 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) andbundle installbefore running commands. bundle installinstalls development and runtime dependencies.bundle exec rspecruns the full test suite.bundle exec guardruns specs on file changes (perGuardfile).bundle exec rubocopchecks style against.rubocop.yml.bundle exec rake buildbuilds the gem package (Bundler gem tasks).
Coding Style & Naming Conventions
- Ruby with 2-space indentation.
- Use standard Ruby naming:
snake_casefor methods/variables andCamelCasefor 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 theCommandLineReportermodule.
Testing Guidelines
- RSpec is the test framework; files use the
*_spec.rbnaming 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.
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.
- 2d ago First seen · 41 lines · 480 tokens per session scan A 9c23b196b3ee
command_line_reporter AGENTS.md is an instructions file published in the GitHub repository wbailey/command_line_reporter (426 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 480 tokens to every session, about $0.0024 per session on Opus 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.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.