Borrowing it
Nothing to install: this file belongs to Genuifx/ccem. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Genuifx/ccem/main/AGENTS.mdgit clone --depth 1 https://github.com/Genuifx/ccemWrote 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/genuifx/ccem/agents-md)<a href="https://agentmods.dev/instructions/genuifx/ccem/agents-md"><img src="https://agentmods.dev/badge/instructions/genuifx/ccem/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.
<a href="https://agentmods.dev/instructions/genuifx/ccem/agents-md"><img src="https://agentmods.dev/badge/instructions/genuifx/ccem/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02578 | $0.02578 |
| Opus 5.5 | $0.01031 | $0.01031 |
| Sonnet 5.5 | $0.00516 | $0.00516 |
| Haiku 4.5 | $0.00258 | $0.00258 |
Grade A, and why
ccem 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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Codex Environment Manager (ccem) — monorepo for CLI + Tauri desktop app, managing multiple API configurations for Codex.
How To Use This File
This file is intentionally split into three layers:
- Strategy philosophy Calibrate how to think in this repo. Prefer thinking frameworks over brittle step-by-step scripts.
- Minimal complete toolset Define the smallest reliable set of tools and workflows that closes the loop for real delivery.
- Necessary facts Provide repo-specific technical facts, constraints, and commands. These are reasoning inputs, not substitutes for judgment.
Use this file to strengthen autonomous judgment, not to replace it. If the user explicitly asks for a different flow, the user request wins.
1. Strategy Philosophy
Think in frameworks, not cargo-culted rules
- Do not optimize for “following the checklist”.
- Optimize for end-to-end closure: understand the task, isolate the change, implement it, verify it, and show evidence.
- Treat repo guidance as a decision framework. If a stronger, simpler path is clearly better for the current task, take it and explain why.
Resist model inertia
- Do not stop at the first plausible answer, the first green build, or the first file that looks relevant.
- For non-trivial work, ask: what would make this feel genuinely closed-loop instead of merely edited?
- When a change touches app behavior, validate the real user flow instead of assuming code inspection is enough.
Prefer proof over narration
- “Fixed” means commands ran or the flow was actually exercised.
- A summary without verification evidence is not a finished task.
- When the repo offers a direct validation path, prefer it over indirect confidence.
Keep guidance abstract, keep facts concrete
- Strategy should stay high-level and reusable.
- Tooling guidance should describe capability boundaries, not micromanage every motion.
- Repo facts should be concrete and testable.
Interaction design philosophy
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.
- 1mo ago Changed 28e6190df4a0
- 1mo ago First seen · 220 lines · 2,578 tokens per session scan A 6cbc7467cfab
ccem AGENTS.md is an instructions file published in the GitHub repository Genuifx/ccem (23 stars, last pushed today), licensed Apache-2.0. It adds 2,578 tokens to every session, about $0.0103 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-08-30.
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).
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.
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).
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 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).
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.