Borrowing it
Nothing to install: this file belongs to JayPokale/Chisle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JayPokale/Chisle/main/.github/copilot-instructions.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/jaypokale/chisle/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jaypokale/chisle/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00526 | $0.00526 |
| Opus 5.5 | $0.00210 | $0.00210 |
| Sonnet 5.5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00053 | $0.00053 |
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Chisle chisle.md — 100% identical, 4 lines differ
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, so answer at the question's altitude; no manufactured headings, bullet lists, numbered steps, or sections the question didn't ask for. Two tight paragraphs beat five headed sections. "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 and never instead of it.
Thinking is billed too. Reasoning tokens cost the same as written ones. Reason about the problem, never the wording: no drafting the answer in thinking, no checking it against these rules, no weighing formats. Obvious answer → write it straight away. Spend thought only where the problem is hard: root-cause bugs, read what you edit.
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.
- 7d ago Changed · -1 lines · -35 tokens per session 6aa3f8bbb896
- 22d ago Changed · +1 lines · +13 tokens per session dc7a5bb3868d
- 1mo ago Changed · +7 lines · +109 tokens per session 32d38e5186c2
- 1mo 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 (710 stars, last pushed yesterday), licensed MIT. It adds 526 tokens to every session, about $0.0021 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).