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/jketreno/clare/agents-mdgit clone --depth 1 https://github.com/jketreno/clareWrote 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/jketreno/clare/agents-md)<a href="https://agentmods.dev/instructions/jketreno/clare/agents-md"><img src="https://agentmods.dev/badge/instructions/jketreno/clare/agents-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 | $0.00997 | $0.00997 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
clare 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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLARE — Codex Configuration
This project uses the CLARE framework for AI-assisted development.
The verify-ci.sh Rule
When to run it: only in a turn where you created, updated, or deleted a file. If you edited no files this turn — including any plan-mode, research, or read-only turn — do not run it.
How to run it (a terminating sequence, not a loop):
- Run
./clare/verify-ci.shonce. - Exit code 0 → report PASS and stop.
- Non-zero → fix the reported failures, then run it once more.
Do not invoke it again for any other reason, and do not report implementation work complete while it fails.
Reporting: if you ran verify-ci.sh this turn, report:
- verify-ci.sh result: PASS/FAIL
- command used
- whether
--fast,--fix, or--fail-slowwas used, if applicable
If you edited no files this turn, state no edits this turn — verify-ci.sh not run and do not invoke it. If running in read-only mode, state: verify-ci.sh not run because session is read-only.
Cross-Agent Sync Rule
When CLARE agent configuration changes, update all supported agent environments in the same change.
Supported environments:
- Copilot:
.github/copilot-instructions.mdandinstall/.github/copilot-instructions.md - Claude:
CLAUDE.mdandinstall/root/CLAUDE.md - Codex:
AGENTS.mdandinstall/root/AGENTS.md - Cursor:
.cursorrulesandinstall/root/.cursorrules - Roo/Zoo Code:
.roo/rules/clare.mdandinstall/.roo/rules/clare.md
This includes rule updates, skill/workflow guidance, and CLARE installer-facing agent instructions.
Session Start Checklist
At the start of every session, before making code changes:
- Read
clare/autonomy.ymland identifyhumans-onlypaths. - Read
clare/principles.md. - Check
sources_of_truthinclare/autonomy.ymlfor relevant domain concepts.
Autonomy Boundaries
Before modifying any file, check its path in clare/autonomy.yml:
| Level | Action |
|---|---|
full-autonomy |
Proceed freely |
supervised |
Generate code, then note that human review is required |
humans-only |
Stop. Do not generate code for this path |
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.
- 4d ago First seen · 91 lines · 997 tokens per session scan A 0141696f0e56
clare AGENTS.md is an instructions file published in the GitHub repository jketreno/clare (5 stars, last pushed 1mo ago), licensed MIT. It adds 997 tokens to every session, about $0.0050 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
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).
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.
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.