fak: Instructions file for GitHub Copilot

.github/copilot-instructions.md

fak copilot-instructions.md is an instructions file for GitHub Copilot from anthony-chaudhary/fak. It costs 580 tokens per session, scanned A, original, Apache-2.0.

A GitHub Copilot instruction file describing the required workflow for automated contributors to the fak repository.

In plain words
What is it for?
Guiding Copilot while it works on the fak codebase.
Why use it?
It gives Copilot project-specific rules for delegation, branches, commits, testing, and shipping changes.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: mentions AGENTS.md.

This is anthony-chaudhary/fak's own configuration. It tells GitHub Copilot how to work on fak itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything fak configures →

Reuse

Borrowing it

Nothing to install: this file belongs to anthony-chaudhary/fak. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/anthony-chaudhary/fak/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/anthony-chaudhary/fak

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for fak copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/anthony-chaudhary/fak/copilot-instructions/github.svg)](https://agentmods.dev/instructions/anthony-chaudhary/fak/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/anthony-chaudhary/fak/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/anthony-chaudhary/fak/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.

agentmods 80×15 button for fak copilot-instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/anthony-chaudhary/fak/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/anthony-chaudhary/fak/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 580 This file is loaded in full into every session.
When invoked 580 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00580 $0.00580
Opus 5.5 $0.00232 $0.00232
Sonnet 5.5 $0.00116 $0.00116
Haiku 4.5 $0.00058 $0.00058

Measured 1mo ago against content hash f2cab372c113, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fak 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 1mo 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.

.github/copilot-instructions.md · 34 lines

What it actually says

Copilot instructions

The canonical agent instructions for this repo are in AGENTS.md — read it first for build/test/run, the repo map, and the rules. Curated doc map: llms.txt. Contributor contract: CONTRIBUTING.md.

Must-know rules (enforced below the agent layer):

  • Delegate substantive work and keep the coordinator context clean — use guarded headless agents or equivalent isolated workers for investigation, implementation, tests, and review. Keep only decisions and compact witnessed evidence in the primary context; independently verify worker effects before landing or reporting them. Direct work is for lightweight coordination and truly trivial tasks. See AGENTS.md.
  • Default is to ship — when the tree is green (make ci), commit AND push unprompted; decide from the work in front of you, you don't wait to be asked. The rules below gate that default (stay on trunk, commit by path, never force-push); if a guard refuses (OFF_TRUNK) or a peer's merge is mid-flight, reconcile in place or stop.
  • Work directly on the trunk (main); never open a feature branch or worktree — the trunk guard refuses off-trunk commits (OFF_TRUNK). The one sanctioned exception: a detached per-worker worktree that lands on main via fak worktree worker prepare|land|reap (build isolation, #1334) — detached and lane-serialized, it is not a branch and never trips OFF_TRUNK. Feature branches and off-trunk commits stay forbidden.
  • Commit by explicit path (git commit -- <paths>, never git add -A); sign off with git commit -s (DCO).
  • Focus on "move forward" over "conclusions" — frame diagnostics, benchmarks, and failed attempts around actionable forward momentum. Rather than defeatist conclusions ("X didn't work ... therefore we suck..."), always identify the concrete next action ("the next step to get better performance is X") and state the next checkable step.
  • Keep code comments succinct: omit comments that restate syntax or narrate each step. Preserve comments that explain non-obvious rationale, invariants, safety, concurrency, compatibility, or exported APIs; prefer clearer code and put durable tutorials in docs.
  • The Go module is the repository root — run go commands from the clone root (go install github.com/anthony-chaudhary/fak/cmd/fak@latest resolves directly).
Changes

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.

  1. 1mo ago Changed · +4 lines · +77 tokens per session f2cab372c113
  2. 1mo ago First seen · 30 lines · 503 tokens per session scan A a8b40c4f82d5

Subscribe to this mod's changes

fak copilot-instructions.md is an instructions file published in the GitHub repository anthony-chaudhary/fak (42 stars, last pushed today), licensed Apache-2.0. It adds 580 tokens to every session, about $0.0023 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-09-03.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,549 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens