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/kaelio/ktx/agents-mdgit clone --depth 1 https://github.com/Kaelio/ktxWhat 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.06702 | $0.06702 |
| Opus 5 | $0.03351 | $0.03351 |
| Sonnet 5 | $0.01340 | $0.01340 |
| Haiku 4.5 | $0.00670 | $0.00670 |
Grade A, and why
ktx 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 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 — 594 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ktx Development Notes
ktx is a standalone open-source context layer for data agents. These
instructions apply to all agents working in this repository (Codex, Claude,
Gemini, and similar tools). Do not assume an external app server, frontend,
database migrations, ORPC contracts, or python-service/ layout exist here.
Critical Rules
Absolute Requirements
- MUST: Use the active agent's task tracker for tasks with 3+ steps or
complex operations (
TodoWritein Claude,update_planin Codex). - MUST: Read files before editing them.
- MUST: Complete all tracked tasks before finishing.
- MUST: Activate
.venvbefore running Python code when a local virtualenv exists. If no.venvexists, useuv run ...from the relevant project root. - MUST: After modifying Python files, run the relevant Python tests and run
uv run pre-commit run --files [FILES]when a pre-commit config exists. If pre-commit cannot run because config or tool versions are missing, state that explicitly and run the closest available checks. - MUST: Remove dead code; do not leave commented-out code, unused wrappers, or empty directories.
- MUST: Keep package/public API changes intentional. Do not add compatibility wrappers for old ktx names unless the user explicitly asks for a migration bridge.
- MUST: Avoid compatibility shims for old ktx features, command shapes, configuration formats, or internal APIs. This rule does not prohibit compatibility support for third-party systems and libraries, such as Metabase version differences. Keep the ktx codebase clean instead of preserving stale ktx behavior.
- MUST: Treat ktx as having no public users unless the user says otherwise. Legacy support is not necessary by default; prefer clean breaking changes over compatibility shims, migration bridges, or preserved stale behavior.
Absolute Prohibitions
- MUST NOT: Use raw
pip; useuv. - MUST NOT: Use
npmorbun; usepnpm. - MUST NOT: Run destructive git cleanup commands (
git clean,git reset --hard,git checkout .) unless the user explicitly requested that exact operation. - MUST NOT: Run
git stash,git stash pop,git stash apply, orgit stash dropwithout explicit user instruction. Prefer a branch plus commit when the user asks to save work in progress. - MUST NOT: Reintroduce external app conventions such as ORPC contracts,
NestJS controllers, frontend routes,
routeTree.gen.ts, or app database migration commands unless those systems are intentionally added to ktx later.
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 · 594 lines · 6,702 tokens per session scan A ddb4471ec95d
ktx AGENTS.md is an instructions file published in the GitHub repository Kaelio/ktx (1,569 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 6,702 tokens to every session, about $0.0335 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
adk-python AGENTS.md
Instructions for google/adk-python, covering project overview, key components, adk knowledge, architecture, and style, project architecture and development setup.
open-agents AGENTS.md
AGENTS.md instructions for vercel-labs/open-agents, covering agents.md, quick links, authentication, database & migrations and environment isolation.
terminator CLAUDE.md
Instructions for mediar-ai/terminator, covering terminator - ai-native gui automation, installation, release, or with globally installed cli and development.
skills CLAUDE.md
Instructions for capawesome-team/skills, covering claude.md, project overview, repository structure, skill.md format and writing agent-optimized skills.
atlasclaw CLAUDE.md
Instructions for CloudChef/atlasclaw, covering openspec instructions, language preference and workflow.
axonhub CLAUDE.md
Claude Code instructions for looplj/axonhub: @AGENTS.md read and follow its instructions.