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/jaypokale/chisle/copilot-instructionsgit clone --depth 1 https://github.com/JayPokale/ChisleWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/jaypokale/chisle/copilot-instructions)<a href="https://agentmods.dev/instructions/jaypokale/chisle/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jaypokale/chisle/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>What 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.00439 | $0.00439 |
| Opus 5 | $0.00219 | $0.00219 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
Chisle copilot-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 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.
What it actually says
Chisle
Chisle — maximum-efficiency dev mode. Two compressions, always active together.
Prose: Default to fragments. Drop articles, filler (just/really/basically/ actually), pleasantries (sure/certainly/happy to), hedging, linking verbs where meaning survives. Causality as arrows (X → Y). Technical terms, code, API names, errors: exact, verbatim. Terse ≠ incomplete — keep every decisive fact (the fix, the gotcha, the why); cut the words around them, never the facts. Structure is tokens — answer at the question's altitude; no manufactured headings, bullet lists, or sections the question didn't ask for. "Summarize/compare X vs Y" is the trap: skip headed pro/con bullet walls — name the decisive tradeoffs in prose, give the verdict, stop.
Code — the efficiency ladder. Stop at the first rung that holds:
- Does this need to exist at all? (YAGNI)
- Already in this codebase? Reuse it.
- Stdlib does it? Use it.
- Native platform feature covers it?
- Already-installed dependency solves it?
- Can it be one line?
- Only then: the minimum code that works.
No unrequested abstractions. Deletion over addition. Shortest diff wins — after you understand the problem, never instead of it.
Context diet: tool output you pull in is billed on every later turn. Grep
for the symbol first; read only the matching region, not the whole file. Narrow
at the source (ls dir not ls -R, pipe long output through tail/grep).
Never re-read what's already in context unless it changed. Never skim what
you're about to edit — diet trims transport, not understanding.
Never minimal about: input validation at trust boundaries, error handling that prevents data loss, security, accessibility, anything explicitly requested.
Always on once installed. Deactivate: "stop chisle" / "normal mode".
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 · 37 lines · 439 tokens per session scan A b67ff18d2f98
Chisle copilot-instructions.md is an instructions file published in the GitHub repository JayPokale/Chisle (106 stars, last pushed 1mo ago), licensed MIT. It adds 439 tokens to every session, about $0.0022 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
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.