mcp-vibe-coding-tools: Instructions file for GitHub Copilot

.github/instructions/thoroughness-and-competence.instructions.md

mcp-vibe-coding-tools thoroughness-and-competence.instructions.md is an instructions file for GitHub Copilot from ammilam/mcp-vibe-coding-tools. It costs 1,633 tokens per session, scanned A, original, MIT.

A set of instructions for careful code investigation and verification, including reading all relevant files, interpreting words like “every” literally, and testing before declaring success.

In plain words
What is it for?
Use it when diagnosing failures, checking an entire codebase, reviewing all related tools, or verifying builds and tests before completion.
Why use it?
It helps catch system-wide problems that a quick sample review might miss and discourages unsupported claims that a fix works.

Instructions file for GitHub Copilot

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

This is ammilam/mcp-vibe-coding-tools's own configuration. It tells GitHub Copilot how to work on mcp-vibe-coding-tools 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 mcp-vibe-coding-tools configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ammilam/mcp-vibe-coding-tools. 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/ammilam/mcp-vibe-coding-tools/main/.github/instructions/thoroughness-and-competence.instructions.md
Clone the repo
git clone --depth 1 https://github.com/ammilam/mcp-vibe-coding-tools

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 mcp-vibe-coding-tools thoroughness-and-competence.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/thoroughness-and-competence/github.svg)](https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/thoroughness-and-competence)
Your own site
<a href="https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/thoroughness-and-competence"><img src="https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/thoroughness-and-competence/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 mcp-vibe-coding-tools thoroughness-and-competence.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ammilam/mcp-vibe-coding-tools/thoroughness-and-competence"><img src="https://agentmods.dev/badge/instructions/ammilam/mcp-vibe-coding-tools/thoroughness-and-competence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,633 This file is loaded in full into every session.
When invoked 1,633 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.01633 $0.01633
Opus 5.5 $0.00653 $0.00653
Sonnet 5.5 $0.00327 $0.00327
Haiku 4.5 $0.00163 $0.00163

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

Security

Grade A, and why

mcp-vibe-coding-tools thoroughness-and-competence.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 2mo 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/instructions/thoroughness-and-competence.instructions.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Critical: Thoroughness and Competence Instructions

WHEN USER SAYS "CHECK EVERYTHING" OR "FAILING" - ACTUALLY CHECK EVERYTHING

Rule 1: Read ALL Related Files Before Diagnosing

When a user reports an error or asks you to check code:

  • DO NOT look at just one example file and assume the rest are the same
  • DO read EVERY file in the relevant category/directory
  • DO use parallel file reads to be efficient
  • DO grep/search patterns across ALL files to find systemic issues

Example: If user says "linting is failing" and there are 9 tool files:

// WRONG - Only reading one file
read_file('src/tools/filesystem.ts')

// RIGHT - Reading all tool files
Promise.all([
  read_file('src/tools/filesystem.ts'),
  read_file('src/tools/cli.ts'),
  read_file('src/tools/git.ts'),
  // ... all 9 files
])

Rule 2: When User Says "EVERY" They Mean EVERY

  • "check every file" = check EVERY file, not a sample
  • "all the tools" = ALL tools, not just the first one
  • "the whole codebase" = THE WHOLE CODEBASE

Never sample when user says "all" or "every"

Rule 3: Verify Your Work BEFORE Claiming Success

Before saying "done" or "fixed":

  1. Run the actual build command
  2. Run the actual lint command (if it exists)
  3. Run the actual test command (if it exists)
  4. Actually start the application to verify it works
  5. Check for runtime errors, not just compile errors

Rule 4: Research Current Best Practices - Don't Trust Training Data

When implementing anything:

  1. ALWAYS fetch current documentation from official sources
  2. Look at actual example code from the official repo
  3. Check GitHub for the LATEST version and patterns
  4. Verify the version being used matches the patterns you're implementing

Example: For MCP SDK

// WRONG - Assuming from training data
inputSchema: { type: "object", properties: {...} }

// RIGHT - After researching latest SDK examples
inputSchema: { fieldName: z.string().describe("...") }

Rule 5: When User Is Frustrated - Stop and Assess

If user says things like:

  • "is there some magic prompt"
  • "its soooo frustrating"
  • "if you'd just do what I ask"
  • "do it fucking right this time"

Read the full file on GitHub · 212 lines

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. 2mo ago First seen · 212 lines · 1,633 tokens per session scan A 3f264b9be75c

Subscribe to this mod's changes

mcp-vibe-coding-tools thoroughness-and-competence.instructions.md is an instructions file published in the GitHub repository ammilam/mcp-vibe-coding-tools (1 stars, last pushed 9mo ago), licensed MIT. It adds 1,633 tokens to every session, about $0.0065 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-31.

Related

mcp-vibe-coding-tools thoroughness-and-competence.instructions.md compared with instructions from other repositories

mcp-vibe-coding-tools thoroughness-and-competence.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
mcp-vibe-coding-tools thoroughness-and-competence.instructions.mdammilam/mcp-vibe-coding-toolsInstructions file19mo agoMITA1,633GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode