cuecards: Instructions file for Codex

AGENTS.md

cuecards AGENTS.md is an instructions file for Codex, OpenCode from opencue/cuecards. It costs 1,666 tokens per session, scanned A, original, MIT.

A repository instruction file that tells coding agents how cue works, where its profiles and resources live, and which rules they must follow.

In plain words
What is it for?
Use it as the starting reference for cue bootstrap behavior, profile resources, rule syncing, paths, and platform-specific setup.
Why use it?
It gives agents the project context and operating constraints they need before changing or maintaining the repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

This is opencue/cuecards's own configuration. It tells Codex and OpenCode how to work on cuecards itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cuecards configures →

Reuse

Borrowing it

Nothing to install: this file belongs to opencue/cuecards. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/opencue/cuecards/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/opencue/cuecards

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 cuecards AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/opencue/cuecards/agents-md/github.svg)](https://agentmods.dev/instructions/opencue/cuecards/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/opencue/cuecards/agents-md"><img src="https://agentmods.dev/badge/instructions/opencue/cuecards/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cuecards AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/opencue/cuecards/agents-md"><img src="https://agentmods.dev/badge/instructions/opencue/cuecards/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,666 This file is loaded in full into every session.
When invoked 1,666 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01666 $0.01666
Opus 5.5 $0.00666 $0.00666
Sonnet 5.5 $0.00333 $0.00333
Haiku 4.5 $0.00167 $0.00167

Measured 1mo ago against content hash 1d51a681110a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cuecards 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 1mo 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 · 117 lines

How it starts

The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS - cue bootstrap contract

Keep this file lean. It is read by coding agents that help install or maintain cue. Detailed context-budget and install notes live in docs/agent-context-budget.md; open that doc only when the task needs it.

What cue is

cue is an agent profile manager for Claude Code and Codex. It sits between the user's shell and the real claude / codex binary, resolves the active profile from cwd, materializes a per-profile runtime under ~/.config/cue/runtime/, and then execs the real agent.

Key paths:

  • profiles/ - bundled profile definitions.
  • resources/skills/ - installable skills.
  • resources/mcps/ - MCP server configs.
  • resources/rules/ - shared rule library; cue ruler distributes a profile's rules[] into every agent's native rule file (CLAUDE.md, AGENTS.md, .cursorrules, …). Set CUE_RULER_AUTO=1 to sync them on every cue launch (safe mode: never overwrites a hand-written file).
  • setup/ - per-OS install prompts.
  • docs/launch.md - resolve -> materialize -> exec flow.

Bootstrap Rules

  1. Detect the OS before shell work: uname -s for Linux/macOS and $OS / $env:OS for Windows.
  2. Pick one setup file and load only that file:
    • lean stack: setup/lean-cue.md
    • macOS: setup/macos.md
    • Linux: setup/linux.md
    • Windows: setup/windows.md
    • WSL2: use setup/linux.md inside WSL
    • parallel agents: setup/parallel-agents.md, only after lean stack works
  3. Ask before hard-to-reverse or external steps: shell profile edits, existing Claude/Codex config merges, global package installs, sudo, or downloads.
  4. Run one setup phase at a time and verify after each phase.
  5. Keep installs idempotent. Guard each install with an existence check.
  6. Do not auto-enable plugins until the user confirms the exact settings write.
  7. Default profile should stay core unless the user explicitly chooses a broader composite.

Repo Work Rules

  • Preserve user work. Do not revert, reset, or overwrite unrelated changes.
  • Prefer small, source-backed changes over broad rewrites.
  • For repo architecture, feature-flow, or symbol-impact questions, use CodeGraph before broad file reads or grep.
  • For context-heavy files, inspect with wc, narrow rg, sed -n, head, or tail before reading more.
  • Do not paste large fixtures, catalogs, generated files, full logs, or full setup manuals into chat.
  • Verify with the smallest check that proves the touched surface. For profile edits, start with cue validate <profile> plus targeted tests; run cue validate --all only when requested or when a shared loader/materializer change creates real cross-profile risk.
  • For default-profile behavior, source of truth is src/commands/init.ts and profile resolution tests under src/lib/cwd-resolver.test.ts.

Read the full file on GitHub · 117 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. 1mo ago Changed · +16 lines · +226 tokens per session 1d51a681110a
  2. 1mo ago First seen · 101 lines · 1,440 tokens per session scan A ff9ecc35fe7d

Subscribe to this mod's changes

cuecards AGENTS.md is an instructions file published in the GitHub repository opencue/cuecards (6 stars, last pushed yesterday), licensed MIT. It adds 1,666 tokens to every session, about $0.0067 per session on Opus 5.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-09-03.

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 · 9,649 tokens

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.

vercel/next.js · 7,549 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens