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/project-kessel/docs/claude-mdgit clone --depth 1 https://github.com/project-kessel/docsWrote 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/project-kessel/docs/claude-md)<a href="https://agentmods.dev/instructions/project-kessel/docs/claude-md"><img src="https://agentmods.dev/badge/instructions/project-kessel/docs/claude-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.01568 | $0.01568 |
| Opus 5 | $0.00784 | $0.00784 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
docs CLAUDE.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 3d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Configuration
@AGENTS.md
Build and Development Commands
This is an Astro/Starlight documentation site. When working in this repository:
Development workflow
- Start dev server:
npm run dev(serves atlocalhost:4321) - Build the site:
npm run build(runsastro check && astro build, outputs to./dist/) - Preview build:
npm run preview(preview the built site locally)
Before committing
- Always run
npm run buildto verify TypeScript checks and build pass - The CI pipeline runs
astro check && astro build- your changes must pass this - If you get TypeScript errors, the build will fail - fix them before committing
Pre-commit hooks
This repository uses rh-multi-pre-commit for Red Hat security scanning. The hook runs automatically on commit. If you encounter hook failures unrelated to your changes, notify the team.
Claude Code Behavioral Preferences
Content placement
- This repository is for public Kessel documentation only
- Internal Red Hat-specific content (onboarding, hosted config, runbooks, monitoring) belongs in the separate internal docs repo published to InScope
- Do not add Red Hat-specific operational content to this repository
Content creation
- Use
.mdxfor pages needing Astro components (Aside,Tabs,CodeExamples, etc.) - Use
.mdfor pure Markdown content - All frontmatter must include at minimum:
titleanddescription - Follow the Diataxis framework - know if you're writing tutorial, how-to, explanation, or reference
Code examples
- Examples live in
src/examples/organized by topic - Use region markers for selective inclusion:
- C-style languages (Go, TS, Java):
//#region nameand//#endregion - Hash-style languages (Python, Ruby, Bash):
# region nameand# endregion
- C-style languages (Go, TS, Java):
- All important code including error handling must be inside regions
TypeScript
- Strict mode is enforced via
astro/tsconfigs/strict - Path alias
src/*maps to./src/* - Zod schemas use
.optional().default(false)for boolean fields - maintain this pattern
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.
- 3d ago First seen · 88 lines · 1,568 tokens per session scan A b4e5c5f3bdeb
docs CLAUDE.md is an instructions file published in the GitHub repository project-kessel/docs (2 stars, last pushed 9d ago), licensed Apache-2.0. It adds 1,568 tokens to every session, about $0.0078 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-31.
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.