Borrowing it
Nothing to install: this file belongs to josstei/argus-claude. 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/josstei/argus-claude/main/CLAUDE.mdgit clone --depth 1 https://github.com/josstei/argus-claudeWrote 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/josstei/argus-claude/claude-md)<a href="https://agentmods.dev/instructions/josstei/argus-claude/claude-md"><img src="https://agentmods.dev/badge/instructions/josstei/argus-claude/claude-md.svg" alt="Measured on agentmods" 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.01406 | $0.01406 |
| Opus 5 | $0.00703 | $0.00703 |
| Sonnet 5 | $0.00281 | $0.00281 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
argus-claude CLAUDE.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 8d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Argus is a Claude Code plugin for multi-agent code quality and architecture review with cross-validation from multiple LLM providers. Named after Argus Panoptes, the all-seeing giant of Greek mythology.
Architecture
Separation of Concerns
commands/- Entry points only (skills that Claude Code exposes as/argus:*). Orchestration logic lives incommands/review.md.agents/- Individual agent definitions, each with a single responsibility.agents/_shared/- Reusable content fragments included via<!-- @include: path -->markers.schemas/- JSON schemas that define the data contracts between agents.
Multi-Agent Pipeline
Orchestrator (commands/review.md)
→ Analysis Phase: up to 9 agents run in parallel per phase grouping
→ Validation Phase: 5 validators verify findings with evidence
→ External Phase (optional): Codex/Gemini CLI cross-validation
→ Consolidation: merges, deduplicates, scores, generates report
Phase-to-Agent Mapping
| Phase | Analysis Agents | Validator | Depth Required |
|---|---|---|---|
| 1: Architecture | 01-architecture, 02-separation | 1a-architecture | quick+ |
| 2: Hygiene | 03-dead-code, 04-dependencies | 2a-hygiene | quick+ |
| 3: Naming | 05-naming | 3a-naming | standard+ |
| 4: Quality | 06-di-patterns, 07-error-handling, 08-lifecycle | 4a-quality | standard+ |
| 5: Optimization | 09-optimization | 5a-optimization | thorough |
Data Flow Between Agents
Analysis agents → finding.json schema → Validation agents → validation-result.json schema → Consolidation → report.json schema
- finding.json: Individual issue with
id,file,line,violation,severity,description,recommendation(required), plus optionalcurrentPattern,optimalPattern,migrationPath,codeSnippet - validation-result.json: Links back to
originalFindingIdwithvalidationStatus(CONFIRMED/REJECTED/MODIFIED/IMPROVABLE/NEEDS_REVIEW) and requiredevidenceobject - report.json: Final consolidated output with
healthScore(0-100 per domain),verifiedFindings,implementationPlan(phased by severity), and optionalpatternEvolutionRoadmap
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.
- 8d ago First seen · 116 lines · 1,406 tokens per session scan A d48edd88e1b7
argus-claude CLAUDE.md is an instructions file published in the GitHub repository josstei/argus-claude (6 stars, last pushed 7mo ago), licensed MIT. It adds 1,406 tokens to every session, about $0.0070 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-31.
Other instructions, from other repositories
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.
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.
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).
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.