cc-spex: Instructions file for Codex

AGENTS.md

cc-spex AGENTS.md is an instructions file for Codex, OpenCode from rhuss/cc-spex. It costs 229 tokens per session, scanned A, a copy of awesome-spain AGENTS.md, Apache-2.0.

A set of instructions for finishing a coding session in a repository, including follow-up issues, quality checks, commits, and pushing changes to the remote Git repository.

In plain words
What is it for?
Running tests or linters after code changes, recording remaining work, synchronizing with the remote repository, and handing context to the next session.
Why use it?
It prevents unfinished local work from being mistaken for completed work and requires the repository’s final state to be checked.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is rhuss/cc-spex's own configuration. It tells Codex and OpenCode how to work on cc-spex 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 cc-spex configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rhuss/cc-spex. 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/rhuss/cc-spex/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/rhuss/cc-spex

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 cc-spex AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rhuss/cc-spex/agents-md/github.svg)](https://agentmods.dev/instructions/rhuss/cc-spex/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/rhuss/cc-spex/agents-md"><img src="https://agentmods.dev/badge/instructions/rhuss/cc-spex/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 cc-spex AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rhuss/cc-spex/agents-md"><img src="https://agentmods.dev/badge/instructions/rhuss/cc-spex/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 229 This file is loaded in full into every session.
When invoked 229 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 58% copy Near-identical to another mod 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.00229 $0.00229
Opus 5.5 $0.00092 $0.00092
Sonnet 5.5 $0.00046 $0.00046
Haiku 4.5 $0.00023 $0.00023

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

Security

Grade A, and why

cc-spex 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.

Origin

This is a copy

58% identical to awesome-spain AGENTS.md — 110 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 26 lines

What it actually says

Agent Instructions

Landing the Plane (Session Completion)

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

  1. File issues for remaining work - Create issues for anything that needs follow-up
  2. Run quality gates (if code changed) - Tests, linters, builds
  3. PUSH TO REMOTE - This is MANDATORY:
    git pull --rebase
    git push
    git status  # MUST show "up to date with origin"
    
  4. Clean up - Clear stashes, prune remote branches
  5. Verify - All changes committed AND pushed
  6. Hand off - Provide context for next session

CRITICAL RULES:

  • Work is NOT complete until git push succeeds
  • NEVER stop before pushing - that leaves work stranded locally
  • NEVER say "ready to push when you are" - YOU must push
  • If push fails, resolve and retry until it succeeds
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 First seen · 26 lines · 229 tokens per session scan A e28effa1ebe9

Subscribe to this mod's changes

cc-spex AGENTS.md is an instructions file published in the GitHub repository rhuss/cc-spex (120 stars, last pushed 2d ago), licensed Apache-2.0. It adds 229 tokens to every session, about $0.0009 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 58% identical to awesome-spain AGENTS.md, differing in 110 lines, and is treated as a copy.

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,257 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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens