cligent AGENTS.md

A set of AGENTS.md instructions for the cligent project, where written specifications are treated as the source of truth. It explains how to find, follow, update, and check those specifications.

In plain words
What is it for?
Finding relevant specs, checking their structure with spex lint, and keeping specifications synchronized with implementation decisions.
Why use it?
It keeps code and specifications aligned and helps prevent undocumented or contradictory changes.

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/sublang-ai/cligent/agents-md
Clone the repo
git clone --depth 1 https://github.com/sublang-ai/cligent

Made for: Codex, OpenCode.

Per session 292 This file is loaded in full into every session.
When invoked 292 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.00292 $0.00292
Opus 5 $0.00146 $0.00146
Sonnet 5 $0.00058 $0.00058
Haiku 4.5 $0.00029 $0.00029

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

Security

Grade A, and why

cligent 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 12 lines

What it actually says

AGENTS

Specs (Source of Truth)

  • Canonical specs live in @specs/. Start with @specs/map.md for a quick-reference index and @specs/meta.md for the spec format; spec packages live in @specs/packages.
  • Before making changes or suggestions in an area that has a spec, read the relevant spec file(s) first and follow them.
  • Whenever your changes involve any spec, or you make a decision worth recording, keep the specs in sync — don't let them drift.
  • Resolve conflicts spec-first, then iterate freely: an intended change that conflicts with existing spec items is resolved in the specs — or dropped — before coding against it; implementing first to explore an approach is fine, and implementation lessons update this intent's specs, but no intent completes until its specs and code agree.
  • Keep specs lawful per @specs/meta.md — the law itself, not this summary: complete and exact (meta-34), minimal (meta-23), one requirement per item (meta-29), cohesive packages for a shared intent (meta-13), sections per meta-30, relationships and test evidence only as inline citations (meta-14, meta-16, meta-20), integration/system tests only (meta-21, meta-32).
  • Run spex lint to check structure, item IDs, and citations after editing specs; never add trace lines to satisfy an older checker.
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. 2d ago First seen · 12 lines · 292 tokens per session scan A feb325328901

Subscribe to this mod's changes

cligent AGENTS.md is an instructions file published in the GitHub repository sublang-ai/cligent (52 stars, last pushed 4d ago), licensed Apache-2.0. It adds 292 tokens to every session, about $0.0015 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-30.