Borrowing it
Nothing to install: this file belongs to loocor/codmate. 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/loocor/codmate/main/AGENTS.mdgit clone --depth 1 https://github.com/loocor/codmateWrote 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/loocor/codmate/agents-md)<a href="https://agentmods.dev/instructions/loocor/codmate/agents-md"><img src="https://agentmods.dev/badge/instructions/loocor/codmate/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/loocor/codmate/agents-md"><img src="https://agentmods.dev/badge/instructions/loocor/codmate/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.05081 | $0.05081 |
| Opus 5.5 | $0.02032 | $0.02032 |
| Sonnet 5.5 | $0.01016 | $0.01016 |
| Haiku 4.5 | $0.00508 | $0.00508 |
Grade B, and why
codmate AGENTS.md scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Provider tab includes a Model List setting with Default/Opus/Sonnet/Haiku mappings (edited via the mapping sheet); mappings write to Claude env keys in `~/.claude/settings.json`. How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CodMate – AGENTS Guidelines
Purpose
- This document tells AI/code agents how to work inside the CodMate repository (macOS desktop GUI for Codex session management).
- Scope: applies to the entire repo. Prefer macOS SwiftUI/AppKit APIs; avoid iOS‑only placements or components.
Architecture
- App type: macOS SwiftUI app (min macOS 13.5). SwiftPM-only build (no Xcode project).
- Layering (MVVM):
- Models: pure data structures (SessionSummary, SessionEvent, DateDimension, SessionLoadScope, …)
- Services: IO and side effects (SessionIndexer, SessionCacheStore, SessionActions, SessionTimelineLoader, LLMClient)
- ViewModels: async orchestration, filtering, state (SessionListViewModel)
- Views: SwiftUI views only (no business logic)
UI Rules (macOS specific)
- Use macOS SwiftUI and AppKit bridges; do NOT use iOS‑only placements such as
.navigationBarTrailing. - Settings uses macOS 15's new TabView API (
Tab("…", systemImage: "…")) when available; provide a macOS 13.5/14 fallback withtabItem+tag. Container padding is unified (horizontal 16pt, top 16pt).- Tab content uniformly uses
SettingsTabContentcontainer (top-aligned, overall 8pt padding) to ensure consistent layout and spacing across pages.
- Tab content uniformly uses
- Notifications is a top-level Settings page between Terminal and Providers; sections are Common, Codex, Claude Code, and Gemini CLI. Common toggles commit message, title/comment, and copy New/Resume command notifications.
- Providers has been separated from the Codex tab into a top-level Settings page: Settings › Providers manages API key providers, OAuth providers, and Codex/Claude bindings; Settings › Codex only retains Runtime/Privacy/Raw Config (notifications live in Settings › Notifications).
- OAuth providers (Codex/Claude/Gemini/Antigravity/Qwen) are added from the Providers “Add” menu and appear under an OAuth list section with login status and info actions.
- CLI Proxy API status, reroute, and public access live under Providers as shared capabilities; deep diagnostics and installation details live under Settings › Advanced › CLI Proxy API.
- Built-in providers are auto-loaded from an app-bundled
payload/providers.json(managedByCodMate=true). This avoids hardcoding and lets users simply provide API keys; base URLs/models come pre-filled. The list merges bundled entries with~/.codmate/providers.json(user overrides win). - Schema note: use a single provider-level
envKey(preferred) for both Codex and Claude Code connectors. Connector-levelenvKeyremains tolerated for backward compatibility but is considered deprecated and will be ignored at save time to avoid duplication.
- Extensions page (aligned with Providers style):
- Settings › Extensions replaces the old MCP Server page (icon: puzzlepiece.extension).
- Tab 1: MCP Servers (existing list/editor/Uni‑Import UI kept as-is inside the tab); add an Import button to scan Home MCP configs into CodMate.
- Tab 2: Skills (left list + right details split; Add menu supports folder/zip/URL; auto‑sync on changes); add an Import button to scan Home skills into CodMate.
- Commands tab includes Add and Import buttons (Import scans Home command folders into CodMate).
- Import sheets show a vertical list; each row has a right‑aligned strategy control (Skip/Overwrite/Rename) and a context menu “Open in…” to review source files.
- MCP Servers tab keeps: enable toggle on left, edit on right, fixed "Add" button, Uni‑Import preview and confirmation.
- Advanced capabilities (MCPMate download and instructions) remain as a footer/section in MCP Servers tab.
- Search: prefer a toolbar
SearchFieldin macOS, not.searchablewhen exact placement (far right) matters. - Toolbars: place refresh as the last ToolbarItem to pin it at the far right. Keep destructive actions in the detail pane, not in the main toolbar. Command+R and the refresh button also invalidate and recompute global sidebar statistics (projects/path tree and calendar day counts) to reflect new sessions immediately.
- Menu Bar (status item): keep it lightweight with status + quick actions. Show provider/model/sandbox/approval, New/Resume/Search/Open, Recent Projects/Sessions (max 5), Usage summary, Provider switch, Settings/Quit; avoid destructive actions.
- Sidebar (left):
- Top (fixed): "All Sessions" row showing total count and selection state.
- Middle (scrollable): path tree built from
cwdcounts. Rows are compact: default min row height 18, small control size, reduced insets. Single-click selects/expands; double-click applies filter (enter the directory). - Projects mode mirrors the compact list style; Cmd-click toggles multi-selection so users can filter sessions by several projects simultaneously (descendants remain included).
- Bottom (fixed): calendar month view (240pt height) with per-day counts (created/last-updated switch). Always pinned to the bottom with 8pt spacing above. Supports multi-select via Command-click to toggle multiple days; plain click selects a single day (click the same day to clear).
- Only the middle path tree scrolls; top "All Sessions" and bottom calendar remain fixed.
- Sidebar width: min 220pt, max 25% of window width, ideal 260pt.
- Content (middle):
- Default scope loads “today” only for speed.
- Sorting picker is left‑aligned with list content.
- Each row shows: title, timestamps/duration, snippet, and compact metrics (user/assistant/tool/reasoning).
- Status bar (bottom console):
- Docked console bar spans the right-side area (list + detail); sidebar stays full height.
- Resizable via a drag handle; single-line header collapses/expands to multi-line log history.
- Auto mode collapses when idle (no interaction); View menu supports Always Show/Hide.
- Detail (right):
- Sticky action bar at top: Resume, Reveal in Finder, Delete, Export Markdown.
- Add “New” button next to Resume to start a fresh Codex session using the current session’s working directory and model.
- When an embedded terminal is running, show a “Prompts” button beside the folder (Reveal in Finder) icon. Clicking opens a searchable popover of preset command texts; selecting one inserts it into the embedded terminal input (does not auto-execute). User presses Return to run.
- Project-level Extensions are configured in Edit Project: tabs are General, Profile, MCP Servers, Skills (auto‑sync; Gemini project-level toggles disabled). MCP Servers/Skills tabs include Import buttons that scan the project directory. Edit Project window should be resizable.
- Review mode: the list.bullet.rectangle button toggles a full-area Review view (third mode, alongside Conversation and Internal Terminal). In Review mode the detail area is fully occupied by a Git Changes surface. It:
- Auto-detects the Git repo at the session’s working directory (uses
/usr/bin/env gitand a robust PATH). - Lists changed files with stage/unstage toggles and shows a unified diff or a raw file preview (updates on save). Preview is text-only in phase 1.
- Provides a commit box. In full-area mode it uses a multi-line editor with more space.
- Repository authorization is on-demand: when opening Review, the app resolves the repository root (the folder containing
.git) and, if needed, prompts the user with an NSOpenPanel to authorize that folder via a security-scoped bookmark. The Settings page no longer lists authorized repositories; authorization and revoke are managed inline in the Review header.
- Auto-detects the Git repo at the session’s working directory (uses
- “Task Instructions” uses a DisclosureGroup; load lazily when expanded.
- Conversation timeline uses LazyVStack; differentiate user/assistant/tool/info bubbles.
- Timeline & Markdown visibility: Settings › General provides per-surface checkboxes to choose which message types are shown in the conversation timeline and included when exporting Markdown. Defaults: Timeline shows User, Assistant, Reasoning, and Code Edit; Tool Invocation, Token Usage, and Other Info are off by default. Markdown includes only User and Assistant. Environment Context and Turn Context are surfaced in dedicated sections and not configurable; Task Instructions remain in the detail DisclosureGroup; Ghost Snapshot is ignored. Code edits are surfaced as their own message type (extracted from tool calls) and have a separate toggle.
- Turn Context is surfaced in the Environment Context card and is not exposed as a separate toggle or timeline item.
- Context menu in list rows adds: “Generate Title & 100-char Summary” to run LLM on-demand for the selected session.
- Embedded Terminal: One live shell per session when resumed in-app; switching sessions in the middle list switches the attached terminal. The shell keeps running when you navigate away. “Return to history” closes the running shell for the focused session.
- Prompt picker: When embedded terminal is running, a Prompts button opens a searchable list. Prompts are merged from per-project
.codmate/prompts.json(if present) and~/.codmate/prompts.json(user), de-duplicated by command, then layered with a few built‑ins. Items accept either{ "label": "…", "command": "…" }or a plain string (used for both). Selection inserts into the terminal input without executing. The header wrench button opens the preferred file (project if exists, else user). Typing a new command shows “Add …” to create a prompt in the preferred file. Deleting a built‑in prompt records it in a hidden list (prompts-hidden.jsonat project if project prompts exist, else at user), which suppresses that built‑in in the UI. - Terminal shortcuts: (none for now). Clearing via shortcut is not implemented.
- Prompt picker: When embedded terminal is running, a Prompts button opens a searchable list. Prompts are merged from per-project
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 First seen · 236 lines · 5,081 tokens per session scan B 3f4cb20d6adf
codmate AGENTS.md is an instructions file published in the GitHub repository loocor/codmate (664 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 5,081 tokens to every session, about $0.0203 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.