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/mxtommy/kip/projectgit clone --depth 1 https://github.com/mxtommy/KipWhat 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.01164 | $0.01164 |
| Opus 5 | $0.00582 | $0.00582 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
Kip project.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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 118 lines · 1,164 tokens per session scan A 638bddb76dab
Kip project.instructions.md is an instructions file published in the GitHub repository mxtommy/Kip (126 stars, last pushed 21d ago), with no licence file. It adds 1,164 tokens to every session, about $0.0058 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
pymobiledevice3 AGENTS.md
AGENTS.md instructions for doronz88/pymobiledevice3, covering agents, scope, commit expectations, project conventions and where to add things.
pymobiledevice3 CLAUDE.md
Claude Code instructions for doronz88/pymobiledevice3, a project described as: Pure python3 implementation for working with iDevices (iPhone, etc...).
instruments-mcp-server CLAUDE.md
Instructions for nemanjavlahovic/instruments-mcp-server, covering instrumentsmcp, what this is, architecture, key design decisions and adding new parsers.
xcodeinstrumentmcp AGENTS.md
Instructions for eksdev007/xcodeinstrumentmcp, covering agents.md, repository expectations, execution loop, priority order and guardrails.
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.