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/klboke/kkrepo/docsgit clone --depth 1 https://github.com/klboke/kkRepoWhat 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.00147 | $0.00147 |
| Opus 5 | $0.00073 | $0.00073 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
kkRepo docs.instructions.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
Documentation Instructions
- Keep public wording anchored to implemented behavior.
- Use
kkRepo/kkrepoas the product name. UseNexusonly as a compatibility or migration reference. - Keep Chinese docs under
docs/zhand English docs underdocs/enaligned when both describe the same feature. - Prefer version-precise claims and explicit caveats over broad roadmap wording.
- For development and deployment docs, include Java 25 and the
server -amMaven guidance where relevant. - Do not include internal deployment details in public-facing docs unless the file is explicitly about local development or deployment.
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 · 13 lines · 147 tokens per session scan A 56331baee2bd
kkRepo docs.instructions.md is an instructions file published in the GitHub repository klboke/kkRepo (251 stars, last pushed 3d ago), licensed Apache-2.0. It adds 147 tokens to every session, about $0.0007 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
supply-chain-hardening AGENTS.md
Instructions for jlevy/supply-chain-hardening, covering agents.md, common intents, safety rule for agents, untrusted repos and repo-supplied agent config is untrusted input.
VTCode AGENTS.md
Instructions for vinhnx/VTCode, covering agents.md, rules, detailed guides, workspace and per-module guidance.
api2mcp4j CLAUDE.md
Claude Code instructions for TheEterna/api2mcp4j, covering claude.md, 项目概述, 顶层授权框架（必读）, 开发心法与规范导航 and 通用心法（docs/rules/global/，所有会话默认生效）.
mail-time AGENTS.md
Instructions for veliovgroup/mail-time, covering agents.md, mission, topology / tuning (read readme for use-cases), multiple instances — encouraged and one mail host: 2–8 servers.
packrehearsal AGENTS.md
Instructions for liyuqin606-del/packrehearsal, covering packrehearsal instructions for codex, mission, before editing, safety invariants and implementation expectations.
deptrust AGENTS.md
Instructions for clidey/deptrust, covering what this is, commands, architecture, adding an ecosystem and distribution.