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/ceorkm/kratos-cli/agents-mdgit clone --depth 1 https://github.com/ceorkm/kratos-cliWhat 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.00276 | $0.00276 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
kratos-cli 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 2d 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.
What it actually says
Memory System
This project uses Kratos CLI for persistent memory across coding sessions.
Commands
- Context:
npx kratos-cli context— compact memory block (pinned + decisions + recent) - Save:
npx kratos-cli save "description" --tags tag1,tag2 --importance 3 - Search:
npx kratos-cli search "query" - Ask:
npx kratos-cli ask "question about the project" - Recent:
npx kratos-cli recent --limit 10 - Status:
npx kratos-cli status - Get:
npx kratos-cli get <memory-id> - Forget:
npx kratos-cli forget <memory-id> - Scan:
npx kratos-cli scan "text to check" --redact
Setup (once per project)
Run npx kratos-cli hooks install — installs session memory injection, auto-capture, and git commit capture for Claude Code.
When to save
- Architecture decisions
- Bug fixes (what was wrong + how you fixed it)
- Important codebase patterns
- Feature implementations
- User preferences and conventions
When to search
- Start of each session — get context about current work
- When asked about past decisions
- Before making changes to understand existing patterns
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.
- 2d ago First seen · 30 lines · 276 tokens per session scan A 905f08913bde
kratos-cli AGENTS.md is an instructions file published in the GitHub repository ceorkm/kratos-cli (10 stars, last pushed 24d ago), licensed MIT. It adds 276 tokens to every session, about $0.0014 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.