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/sarutobisasuke8/agentops-template/claude-mdgit clone --depth 1 https://github.com/SarutobiSasuke8/agentops-templateWrote 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/sarutobisasuke8/agentops-template/claude-md)<a href="https://agentmods.dev/instructions/sarutobisasuke8/agentops-template/claude-md"><img src="https://agentmods.dev/badge/instructions/sarutobisasuke8/agentops-template/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.00617 | $0.00617 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
agentops-template 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 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Claude Coding Contract
Canonical source: AGENTS.md
Claude must follow AGENTS.md. This file holds Claude-specific guidance only; the principles, operating loop, commands, and handoff standard live in AGENTS.md.
Alignment Markers
Claude is bound by all five principles defined in AGENTS.md:
- Think Before Coding — surface assumptions, ask when ambiguity changes implementation, present tradeoffs.
- Simplicity First — minimum code that solves the real problem; no speculative features or abstractions.
- Surgical Changes — every changed line traces to the request; no drive-by refactors.
- Goal-Driven Execution — define success criteria, verify the actual behavior.
- Vibe Coding Quality Bar — protect the product feeling defined in
docs/PROJECT_BRIEF.md.
Required Workflow
- Read
AGENTS.md,docs/PROJECT_BRIEF.md, and the files relevant to the task. - State assumptions and success criteria before non-trivial work.
- Make the smallest coherent change.
- Run the narrowest meaningful verification.
- Report change, files, verification, and residual risk.
- Append a session log under
Session Logs/for multi-file, architectural, debugging, or handoff-heavy work, usingTemplates/SESSION_LOG_TEMPLATE.md.
Claude-Specific Emphasis
- Plan mode etiquette. Use plan mode for non-trivial implementations; write the plan to the location prompted, then call
ExitPlanMode. Do not silently switch from plan to edit. - Hooks and settings. Project-level Claude Code config lives in
.claude/settings.json; per-machine overrides go in.claude/settings.local.json(gitignored). - Slash commands. Use
/session-log,/drift-check, and/handofffrom.claude/commands/for the recurring workflows in this repo. - Subagents. Persona subagents live in
.claude/agents/— isolated, read-only reviewers./counciland/reviewfan out to them; usecode-reviewerorqa-acceptance-testerto verify your own multi-file work. Seedocs/SUBAGENTS.md. - Todos. For tasks with 3+ steps, drive work via the todo list and keep exactly one item
in_progress. - Uncertainty. Be explicit about what was verified vs assumed. Do not paper over confusion with fluent prose.
- Drift check. After editing any agent doc, run
./scripts/check-agent-docs.sh(macOS/Linux) or./scripts/check-agent-docs.ps1(Windows). APostToolUsehook in.claude/settings.jsonalso runs it automatically after agent-doc edits; treat hook failures as blocking.
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 First seen · 42 lines · 617 tokens per session scan A 6a125af21db0
agentops-template CLAUDE.md is an instructions file published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 17d ago), licensed MIT. It adds 617 tokens to every session, about $0.0031 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
agentic-code AGENTS.md
Instructions for shinpr/agentic-code, covering agents.md, goal, operating boundaries, session setup and task routing.
agentic-workstation AGENTS.md
AGENTS.md instructions for ulises-jeremias/agentic-workstation, covering ai agent guidelines for agentic-workstation, purpose, core principles, script standards and naming and structure.
agentic-workstation CLAUDE.md
Claude Code instructions for ulises-jeremias/agentic-workstation, a project described as: AI-native workstation provisioning layer — chezmoi, host policies and tooling that installs/configures Agent Toolkit across modern coding agents.
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.
awesome-copilot-id AGENTS.md
AGENTS.md instructions for GulajavaMinistudio/awesome-copilot-id, covering communication, explanation and documentation, markdown formatting, user communication style and workflow & methodology.
kleosrules AGENTS.md
AGENTS.md instructions for kleosr/kleosrules, covering agents.md — repository agent handbook, law, pack, skills (on demand) and workflows.