clare AGENTS.md

clare AGENTS.md is an instructions file for Codex, OpenCode from jketreno/clare. It costs 997 tokens per session, scanned A, original, MIT.

Project instructions for Clare, an AI-assisted development framework. They define when to run the project’s verification script, how to report its result, and how to keep agent configurations synchronized.

In plain words
What is it for?
Following session-start rules, running and reporting verify-ci.sh after edits, and updating supported Copilot and other agent configuration files together.
Why use it?
They provide a consistent check after file changes and prevent configuration differences between supported agent environments.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/jketreno/clare/agents-md
Clone the repo
git clone --depth 1 https://github.com/jketreno/clare

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for clare AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jketreno/clare/agents-md.svg)](https://agentmods.dev/instructions/jketreno/clare/agents-md)
Your own site
<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>
Per session 997 This file is loaded in full into every session.
When invoked 997 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 0141696f0e56, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

AGENTS.md · 91 lines

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):

  1. Run ./clare/verify-ci.sh once.
  2. Exit code 0 → report PASS and stop.
  3. 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-slow was 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.md and install/.github/copilot-instructions.md
  • Claude: CLAUDE.md and install/root/CLAUDE.md
  • Codex: AGENTS.md and install/root/AGENTS.md
  • Cursor: .cursorrules and install/root/.cursorrules
  • Roo/Zoo Code: .roo/rules/clare.md and install/.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:

  1. Read clare/autonomy.yml and identify humans-only paths.
  2. Read clare/principles.md.
  3. Check sources_of_truth in clare/autonomy.yml for 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

Read the full file on GitHub · 91 lines

Changes

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.

  1. 4d ago First seen · 91 lines · 997 tokens per session scan A 0141696f0e56

Subscribe to this mod's changes

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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens