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.
npx agentmods add instructions/0-ai-ug/cate/agents-mdgit clone --depth 1 https://github.com/0-AI-UG/cateWrote 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/0-ai-ug/cate/agents-md)<a href="https://agentmods.dev/instructions/0-ai-ug/cate/agents-md"><img src="https://agentmods.dev/badge/instructions/0-ai-ug/cate/agents-md.svg" alt="Measured on agentmods" 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 | $0.01436 | $0.01436 |
| Opus 5 | $0.00718 | $0.00718 |
| Sonnet 5 | $0.00287 | $0.00287 |
| Haiku 4.5 | $0.00144 | $0.00144 |
Grade A, and why
cate 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cate CLAUDE.md — 89% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Before You Code
Read and follow the karpathy-guidelines skill (.Codex/skills/karpathy-guidelines) when writing, reviewing, or refactoring code here — surface assumptions, make surgical changes, keep it simple, and define verifiable success criteria.
Project Overview
Cate is a desktop application that provides an infinite zoomable canvas where editor panels, terminal panels, and browser panels float spatially (similar to Figma/Miro, but for coding). Built with Electron + React + TypeScript, styled with Tailwind CSS.
Build System
The Electron app lives at the project root. Uses electron-vite for bundling.
npm install # install dependencies
npm run dev # start dev server with hot reload
npm run build # production build
npm test # run vitest suite
Tests use Vitest and live alongside the code they cover (*.test.ts / *.test.tsx). A few git-touching tests assume a clean working repo and may fail when the dev tree has a branch named main or local modifications — those failures are environmental, not regressions.
Release Process
Before creating any beta or stable release, update CHANGELOG.md with the
matching version, release date, summary, and categorized user-facing changes.
The changelog entry must be complete before bumping or tagging the release.
Dependencies
Managed via npm (package.json):
- Electron — desktop shell (Chromium + Node.js)
- React 18 + react-dom — UI framework
- xterm.js (
@xterm/xterm) — terminal emulator with WebGL addon - node-pty — native PTY for terminal backend
- Monaco Editor — code editor (VS Code's editor component)
- zustand — lightweight state management
- chokidar — filesystem watching
- simple-git — git operations
- @phosphor-icons/react — icons
- electron-updater — auto-update (GitHub Releases)
Architecture
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.
- 4d ago First seen · 114 lines · 1,436 tokens per session scan A ed0d1ca77d50
cate AGENTS.md is an instructions file published in the GitHub repository 0-AI-UG/cate (2,118 stars, last pushed today), licensed MIT. It adds 1,436 tokens to every session, about $0.0072 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.
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).
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.
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.
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 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).
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.