Borrowing it
Nothing to install: this file belongs to neilberkman/ccrider. 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/neilberkman/ccrider/main/AGENTS.mdgit clone --depth 1 https://github.com/neilberkman/ccriderWrote 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/neilberkman/ccrider/agents-md)<a href="https://agentmods.dev/instructions/neilberkman/ccrider/agents-md"><img src="https://agentmods.dev/badge/instructions/neilberkman/ccrider/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/neilberkman/ccrider/agents-md"><img src="https://agentmods.dev/badge/instructions/neilberkman/ccrider/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.01552 | $0.01552 |
| Opus 5.5 | $0.00621 | $0.00621 |
| Sonnet 5.5 | $0.00310 | $0.00310 |
| Haiku 4.5 | $0.00155 | $0.00155 |
Grade A, and why
ccrider 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core/Interface Separation Philosophy
This codebase follows strict Core/Interface separation based on Saša Jurić's "Towards Maintainable Elixir: The Core and the Interface".
Principles
CORE Layer (internal/core/)
The core contains business logic that applies REGARDLESS of which interface uses it:
- Data Retrieval: All database queries, FTS searches, external API calls
- Business Rules: Filtering out warmup sessions, summary fallback logic, validation
- Data Transformation: Converting raw database rows into domain types
- Domain Types: Structs that represent business concepts (
Session,SessionDetail,SearchResult,Stats) - Pure Business Operations: Logic that would be identical whether you have CLI, TUI, MCP, or web API
Test: "Would this be different for CLI vs TUI vs MCP?"
- NO → Core
- YES → Interface
Examples:
- ✅ CORE: "Get all sessions, excluding those with no meaningful content"
- ✅ CORE: "Search messages using FTS5"
- ✅ CORE: "Calculate last working directory from message history"
- ❌ NOT CORE: "Show 20 sessions" (that's pagination - interface concern)
- ❌ NOT CORE: "Format timestamp as 'Jan 2, 2006'" (that's presentation - interface concern)
INTERFACE Layer (internal/interface/, cmd/ccrider/mcp/)
Interfaces translate between protocols and core:
- Protocol Translation: HTTP, CLI flags, MCP JSON, TUI key bindings
- Input Normalization: Parse
project:foo after:yesterdayinto filter structs - Output Formatting: Convert
time.Timeto "Jan 2" or RFC3339 or "2 hours ago" - Pagination/Limits: Decide to show 20 vs 50 vs 10 results
- Presentation: Colors, tables, progress bars, JSON structure
- Grouping: "Show 3 matches per session" (core returns ALL matches)
Examples:
- ✅ INTERFACE: Strip quotes from user's search query
- ✅ INTERFACE: Apply limit of 50 sessions to display
- ✅ INTERFACE: Group search results by session for display
- ✅ INTERFACE: Format date as "2 days ago" for terminal
- ✅ INTERFACE: Parse
after:2024-01-01from search string
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 · 182 lines · 1,552 tokens per session scan A 13c460d48a02
ccrider AGENTS.md is an instructions file published in the GitHub repository neilberkman/ccrider (136 stars, last pushed 3d ago), licensed MIT. It adds 1,552 tokens to every session, about $0.0062 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.