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 skills/vanillagreencom/kendex/bot-instructionsnpx skills add vanillagreencom/kendex --skill bot-instructionsgit 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.00051 | $0.02086 |
| Opus 5 | $0.00026 | $0.01043 |
| Sonnet 5 | $0.00010 | $0.00417 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
bot-instructions 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 yesterday.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bot Instructions
Problem with this skill? Run
kendex report— it files to the owning repo automatically. Do not hand-file.
.agents/skills/bot-instructions/scripts/bot-instructions render # write every enabled surface
.agents/skills/bot-instructions/scripts/bot-instructions check # re-render and compare
.agents/skills/bot-instructions/scripts/bot-instructions adopt # take hand-written files over
Flags: --repo, --spec, --staged, --dry-run; bot-instructions --help.
Python 3.11+.
What reads what
| Bot | Reads | Reads from |
|---|---|---|
| Codex | AGENTS.md § Code Review Rules, root plus nearest nested |
undocumented |
| Copilot code review | .github/copilot-instructions.md, .github/instructions/**/*.instructions.md, AGENTS.md |
the pull request head |
| CodeRabbit | .coderabbit.yaml, whole-file, beneath any organization or workspace global override, plus AGENTS.md through knowledge_base.code_guidelines.filePatterns |
the pull request head |
| Qodo | .pr_agent.toml, best_practices.md, REVIEW.md |
the default branch root |
| Macroscope | .macroscope/ignore.md, .macroscope/correctness/*.md, plus .macroscope/check-run-agents/** and .macroscope/approvability.md, which this package never writes |
the pull request's most recent commit, or the default branch for a fork |
Routing per block and surface: schemas/renders.md § Doctrine routing. Vendor caps: references/limits.md.
The pieces
doctrine (§ Doctrine below) the rules that must reach two or more bots
bot-instructions.toml one per repo, at the repo root
├─ [repo] what this repo is, in the bots' own words
├─ [bots] which bot capabilities are live here
├─ [cadence] when each bot re-reviews
├─ [exclusions] what is not this repo's code to fix
├─ [[surface]] a path set and what a reviewer must know there
└─ [doctrine] per-repo additions to a doctrine block
│
▼ render
AGENTS.md § Code Review Rules .coderabbit.yaml
.github/copilot-instructions.md .pr_agent.toml + best_practices.md
.github/instructions/*.md .macroscope/
A [[surface]] reaches Copilot, CodeRabbit and Macroscope, plus Qodo through best_practices.md when [bots] qodo_best_practices is on. Only Macroscope honors exclude_globs, so narrow globs where scoping matters. Keys: schemas/repo-toml.md. Validators: schemas/validators.md.
What ships with it
47 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 4.5 KB
- references/checklist.md 17 KB
- references/limits.md 13 KB
- references/validators.md 721 B
- schemas/renders.md 40 KB
- schemas/repo-toml.md 31 KB
- schemas/validators.md 40 KB
- scripts/bot-instructions 1.1 KB
- scripts/lib/__init__.py 0 B runs code
- scripts/lib/cli.py 4.2 KB runs code
- scripts/lib/config.py 10 KB runs code
- scripts/lib/constants.py 4.8 KB runs code
- scripts/lib/errors.py 2.3 KB runs code
- scripts/lib/fsutil.py 1.9 KB runs code
- scripts/lib/globs.py 7.0 KB runs code
- scripts/lib/jsonschema.py 5.7 KB runs code
- scripts/lib/main.py 249 B runs code
- scripts/lib/manifest.py 6.2 KB runs code
- scripts/lib/markdown.py 2.3 KB runs code
- scripts/lib/marker.py 3.9 KB runs code
- scripts/lib/model.py 6.9 KB runs code
- scripts/lib/refusals.py 5.7 KB runs code
- scripts/lib/render_coderabbit.py 10 KB runs code
- scripts/lib/render_markdown.py 7.0 KB runs code
- scripts/lib/render_qodo.py 3.5 KB runs code
- scripts/lib/render.py 7.7 KB runs code
- scripts/lib/run.py 4.9 KB runs code
- scripts/lib/spec.py 7.3 KB runs code
- scripts/lib/tree.py 5.9 KB runs code
- scripts/lib/validators_bytes.py 8.9 KB runs code
- scripts/lib/validators_repo.py 11 KB runs code
- scripts/lib/verbs.py 7.8 KB runs code
- scripts/lib/writer.py 2.5 KB runs code
- scripts/lib/yamlemit.py 4.4 KB runs code
- tests/adopt.test.sh 12 KB runs code
- tests/bounds.test.sh 5.9 KB runs code
- tests/coderabbit.test.sh 11 KB runs code
- tests/doctrine-routing.test.sh 13 KB runs code
- tests/exclusions.test.sh 16 KB runs code
- tests/fixtures/canonical.toml 967 B
- tests/fixtures/coderabbit-schema.json 14 KB
- tests/globs.test.sh 7.0 KB runs code
- tests/lib/harness.sh 7.2 KB runs code
- tests/render.test.sh 19 KB runs code
- tests/repo-state.test.sh 18 KB runs code
- tests/staged.test.sh 7.7 KB runs code
- tests/toml-schema.test.sh 18 KB runs code
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.
- yesterday First seen · 161 lines · 51 tokens per session scan A 4a8192e91ce0
bot-instructions is a skill published in the GitHub repository vanillagreencom/kendex (65 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 2,086 once invoked, about $0.0003 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-09-02.
Other skills, from other repositories
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
prose-review
Review prose written for others -- user-facing docs, prompts for other LLMs, inline comments, docstrings, and other-facing messages -- for local jargon leakage, orphaned references, missing grounding, and audience or genre misfit.
text-search
Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.
repoprompt-tool-guidance-refresh
Refresh RepoPrompt tool guidance when the CLI/MCP surface changes. Tracks RepoPrompt CE (rpce-cli, the maintained target) across versions, and can diff the frozen Classic CLI (rp-cli) against CE. Uses /.pi/agent/skills/repoprompt-tool-guidance-refresh/scripts/track-rp-version.sh to capture/diff --help and -l (tool…
xcodebuildmcp
Build/test Xcode projects via the XcodeBuildMCP MCP server using a local CLI wrapper for pi (no MCP support). Use when the user mentions Xcode, xcodebuild, iOS builds/tests, or XcodeBuildMCP.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.