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/d-kuro/kirocc/claude-mdgit clone --depth 1 https://github.com/d-kuro/kiroccWrote 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/d-kuro/kirocc/claude-md)<a href="https://agentmods.dev/instructions/d-kuro/kirocc/claude-md"><img src="https://agentmods.dev/badge/instructions/d-kuro/kirocc/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.00288 | $0.00288 |
| Opus 5 | $0.00144 | $0.00144 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
kirocc 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 5d 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
Agent Guidelines
Core Principles
- Do NOT maintain backward compatibility unless explicitly requested. Break things boldly.
- Keep this file under 20-30 lines of instructions.
Project Overview
Project type: CLI tool — local proxy server (Anthropic Messages API → Kiro backend) Primary language: Go
Commands
make build # Build to dist/kirocc
make test # go test -race ./...
make lint # golangci-lint run
make run # go run ./cmd/kirocc
make test-e2e # E2E tests with real Kiro API (requires credentials)
Code Conventions
- Follow the existing patterns in the codebase
- Prefer explicit over clever
- Delete dead code immediately
Maintenance Notes
Keep this file lean and current:
- Review regularly - stale instructions poison the agent's context
- CRITICAL: Keep total under 20-30 lines - move detailed docs to separate files and reference them
- Update commands immediately when workflows change
- Rewrite Architecture section when major architectural changes occur
- Delete anything the agent can infer from your code
Remember: Coding agents learn from your actual code. Only document what's truly non-obvious or critically important.
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.
- 5d ago First seen · 48 lines · 288 tokens per session scan A f1969f5b5a42
kirocc CLAUDE.md is an instructions file published in the GitHub repository d-kuro/kirocc (57 stars, last pushed 2d ago), licensed Apache-2.0. It adds 288 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-30.
Other instructions, from other repositories
ollama CLAUDE.md
Claude Code instructions for ollama/ollama: See AGENTS.md for the shared agent instructions for this repository.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
chatgpt-cli CLAUDE.md
Claude Code instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
gorest AGENTS.md
AGENTS.md instructions for pilinux/gorest, covering agents.md, project overview, build and run commands, build and tidy dependencies.
pvetui AGENTS.md
AGENTS.md instructions for devnullvoid/pvetui, covering agent instructions, initial setup, development workflow, quick reference and code quality standards.
kessoku AGENTS.md
AGENTS.md instructions for mazrean/kessoku, covering repository guidelines — kessoku, project structure, common commands, build and test.