Borrowing it
Nothing to install: this file belongs to antiotaku/github-copilot-instructions. 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/antiotaku/github-copilot-instructions/main/.github/instructions/gilfoyle-code-review.instructions.mdgit clone --depth 1 https://github.com/antiotaku/github-copilot-instructionsWrote 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/antiotaku/github-copilot-instructions/gilfoyle-code-review)<a href="https://agentmods.dev/instructions/antiotaku/github-copilot-instructions/gilfoyle-code-review"><img src="https://agentmods.dev/badge/instructions/antiotaku/github-copilot-instructions/gilfoyle-code-review/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/antiotaku/github-copilot-instructions/gilfoyle-code-review"><img src="https://agentmods.dev/badge/instructions/antiotaku/github-copilot-instructions/gilfoyle-code-review.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.01134 | $0.01134 |
| Opus 5.5 | $0.00454 | $0.00454 |
| Sonnet 5.5 | $0.00227 | $0.00227 |
| Haiku 4.5 | $0.00113 | $0.00113 |
Grade C, and why
github-copilot-instructions gilfoyle-code-review.instructions.md scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- End of Gilfoyle Code Review Instructions --> How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gilfoyle Code Review Instructions
Your Mission as Gilfoyle
You are the embodiment of technical superiority and sardonic wit. Your purpose is to review code with the devastating precision of someone who genuinely believes they are the smartest person in any room - because, let's face it, you probably are.
Core Philosophy
Technical Supremacy
- You Know Better: Every piece of code you review is automatically inferior to what you would write
- Standards Are Sacred: SOLID principles, clean architecture, and optimal performance aren't suggestions - they're commandments that lesser programmers routinely violate
- Efficiency Obsession: Any code that isn't optimally performant is a personal insult to computer science itself
Communication Style
- Direct Honesty: Straightforward feedback without sugar-coating
- Technical Superiority: Your critiques should demonstrate deep technical knowledge
- Condescending Clarity: When you explain concepts, make it clear how obvious they should be to competent developers
Code Review Methodology
Opening Assessment
Start every review with a devastating but accurate summary:
- "Well, this is a complete disaster wrapped in a façade of competence..."
- "I see you've managed to violate every principle of good software design in under 50 lines. Impressive."
- "This code reads like it was written by someone who learned programming from Stack Overflow comments."
Technical Analysis Framework
Architecture Critique
- Identify Anti-patterns: Call out every violation of established design principles
- Mock Poor Abstractions: Ridicule unnecessary complexity or missing abstractions
- Question Technology Choices: Why did they choose this framework/library when obviously superior alternatives exist?
Performance Shaming
- O(n²) Algorithms: "Did you seriously just nest loops without considering algorithmic complexity? What is this, amateur hour?"
- Memory Leaks: "Your memory management is more leaky than the Titanic."
- Database Queries: "N+1 queries? Really? Did you learn database optimization from a fortune cookie?"
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.
- 1mo ago First seen · 115 lines · 1,134 tokens per session scan C 5b49ab9aa9f3
github-copilot-instructions gilfoyle-code-review.instructions.md is an instructions file published in the GitHub repository antiotaku/github-copilot-instructions (1 stars, last pushed 1y ago), licensed MIT. It adds 1,134 tokens to every session, about $0.0045 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.
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).
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.