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/vanillagreencom/kendex/testsgit clone --depth 1 https://github.com/vanillagreencom/kendexWhat 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.00174 | $0.00174 |
| Opus 5 | $0.00087 | $0.00087 |
| Sonnet 5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
kendex tests.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
- A fixture path the test built itself (
mktemp -d, its own sandbox directory) carries no--, and its absence is not a finding. The--rule covers path values arriving from configuration, argv, or the environment. - A
mktemp -dscratch directory the test removes in its owntrap ... EXITis cleaned up — do not report it as a leak or a missing-cleanup finding. ${arr[@]+"${arr[@]}"}is the quoted empty-array expansion Bash 3.2 requires underset -u, and is the repo-wide idiom — not an unquoted expansion and not a word-splitting defect.
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 · 14 lines · 174 tokens per session scan A 7ea5c1c0c8c0
kendex tests.instructions.md is an instructions file published in the GitHub repository vanillagreencom/kendex (65 stars, last pushed 2d ago), licensed MIT. It adds 174 tokens to every session, about $0.0009 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
pi-agent-browser-native AGENTS.md
Instructions for fitchmultz/pi-agent-browser-native, covering pi-agent-browser-native, product-specific guidance, documentation placement, upstream capability baseline and command reference and tool result categories.
pi-extensions CLAUDE.md
Instructions for MattDevy/pi-extensions, covering claude.md, commands, architecture, data flow and key modules.
supi CLAUDE.md
Instructions for mrclrchtr/supi, covering claude.md, development status, pi docs-first rule, documentation expectations and package layout convention.
pi-extensions AGENTS.md
Instructions for MattDevy/pi-extensions, covering pi-extensions, repository structure, commands (run from repo root), working on a specific package and readme conventions.
pi-codex-goal AGENTS.md
Instructions for fitchmultz/pi-codex-goal, covering pi-codex-goal — agent notes, local pi install policy, verify before finishing and layout.
pi-commandcode-provider AGENTS.md
Instructions for patlux/pi-commandcode-provider, a project described as: pi custom provider for the Command Code API — 18 models including Claude, GPT, DeepSeek, Kimi, GLM, MiniMax, and Qwen.