Borrowing it
Nothing to install: this file belongs to onevcat/argue. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/onevcat/argue/master/AGENTS.mdgit clone --depth 1 https://github.com/onevcat/argueWrote 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.
[](https://agentmods.dev/instructions/onevcat/argue/agents-md)<a href="https://agentmods.dev/instructions/onevcat/argue/agents-md"><img src="https://agentmods.dev/badge/instructions/onevcat/argue/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.
<a href="https://agentmods.dev/instructions/onevcat/argue/agents-md"><img src="https://agentmods.dev/badge/instructions/onevcat/argue/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01446 | $0.01446 |
| Opus 5.5 | $0.00578 | $0.00578 |
| Sonnet 5.5 | $0.00289 | $0.00289 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
argue 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Scope
This file applies to the whole argue repository.
Repo Overview
This repository is a monorepo with three workspace packages under unified versioning — root package.json holds the canonical version and every package carries the same number:
@onevcat/argue: reusable library (published)@onevcat/argue-cli: CLI host (published)@onevcat/argue-viewer: result viewer web app (private,private: true, never published)
The CLI depends on the library through a real semver dependency in packages/argue-cli/package.json. The viewer also consumes @onevcat/argue through a real semver range so its local build graph matches published reality.
Local Development
Use normal monorepo development flow for day-to-day work:
npm install
npm run dev
Useful commands:
npm run check: workspace typechecknpm run test: workspace testsnpm run build: workspace buildnpm run ci:check + test + buildnpm run smoke:pack: tarball install smoke tests for both packagesnpm run release:check:ci + smoke:packnpm run lint: ESLint across reponpm run format:check: Prettier validationnpm run format: format repo
Viewer-only shortcuts (for frontend iteration without rebuilding the library/CLI):
npm run dev:viewer: start the viewer Vite dev servernpm run build:viewer: build the viewer onlynpm run check:viewer: typecheck the viewer onlynpm run test:viewer: run the viewer test suite only
Recommended daily loop:
npm install- make code changes
npm run testnpm run release:checkbefore merging changes that affect packaging, dependency shape, or CLI installability
Package Development Rules
All workspace packages share one version. Do not bump packages individually — every release bumps root + every packages/*/package.json together and @onevcat/argue-cli / @onevcat/argue-viewer always depend on the exact same @onevcat/argue version.
Workflow for any change that will be released:
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.
- 1mo ago First seen · 154 lines · 1,446 tokens per session scan A 72501e7564bc
argue AGENTS.md is an instructions file published in the GitHub repository onevcat/argue (282 stars, last pushed 2mo ago), licensed MIT. It adds 1,446 tokens to every session, about $0.0058 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.
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).
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.
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).
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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.