What is splurge-ai-rules copilot-instructions.md?

A set of GitHub Copilot instructions for the splurge-ai-rules project. It documents development, project organization, design, and Python coding standards.

It is for guiding software work and organizing documents such as research notes, plans, specifications, issue reports, API records, and configuration notes.

It gives contributors shared rules for researching, planning, documenting, and implementing changes. It reduces inconsistent practices across the project.

How jim-schilling/splurge-ai-rules configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to jim-schilling/splurge-ai-rules. 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/jim-schilling/splurge-ai-rules/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/jim-schilling/splurge-ai-rules

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/jim-schilling/splurge-ai-rules/copilot-instructions/github.svg)](https://agentmods.dev/instructions/jim-schilling/splurge-ai-rules/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/jim-schilling/splurge-ai-rules/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jim-schilling/splurge-ai-rules/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/jim-schilling/splurge-ai-rules/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jim-schilling/splurge-ai-rules/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,215 This file is loaded in full into every session.

When invoked 3,215 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.

Model	Per session	Once invoked
Fable 5.1	$0.03215	$0.03215
Opus 5.5	$0.01286	$0.01286
Sonnet 5.5	$0.00643	$0.00643
Haiku 4.5	$0.00321	$0.00321

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

Security

Grade A, and why

splurge-ai-rules 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 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/copilot-instructions.md · 238 lines

How it starts

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

GitHub Copilot Instructions

This document contains coding standards and guidelines for the splurge-ai-rules project. These instructions help maintain consistency and quality across the codebase.

Software Development Lifecycle Standards

Follow Research, Plan, and Implement lifecycle.
Document research in docs/research/research-[description]-[yyyy-MM-dd]-[sequence].md.
Document action plans in docs/plans/plan-[description]-[yyyy-MM-dd]-[sequence].md.
Document requirements and specifications in docs/specs/spec-[description]-[yyyy-MM-dd]-[sequence].md.
Document issues/bugs in docs/issues/issue-[description]-[yyyy-MM-dd]-[sequence].md.
Document apis in docs/apis/api-[description]-[yyyy-MM-dd]-[sequence].md.
Document notes in docs/notes/note-[description]-[yyyy-MM-dd]-[sequence].md.
Document configuration in docs/configuration/configuration-[description]-[yyyy-MM-dd]-[sequence].md.
Research shall include exploration of existing solutions, libraries, and tools.
Plans shall detail requirements, acceptance criteria, testing strategy (e.g. TDD and BDD), and a step-by-step implementation guide.
Each action plan shall be sub-divided into stages (e.g. Stage-1, Stage-2), while stages are subdivided into tasks (e.g. Task-[Stage].1, Task-[Stage].2).
Implementation lifecycle shall always: code failing tests, then implement code, then run tests, then iteratively refactor and run tests until all tests pass.
Every feature must start as a standalone library before integration:
- Develop features as independent, reusable library components first
- Only integrate into larger applications after proving standalone functionality
Software tools, primary libraries, data tools, and development tools must expose their functionality through a CLI. Other software functionality may omit a CLI if appropriate.
If in doubt, prompt user for clarification and mark as [NEEDS CLARIFICATION].
Always ask for user confirmation before making significant changes.
Always ask for user confirmation before deleting files or data.
Always ask for user confirmation before overwriting existing files.
Use git for version control with feature branches and pull requests.
Write clear, concise commit messages in the imperative mood (e.g., "Add feature", "Fix bug").

Read the full file on GitHub · 238 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.

2mo ago First seen · 238 lines · 3,215 tokens per session scan A 6bbeb1b79259

Subscribe to this mod's changes

splurge-ai-rules copilot-instructions.md is an instructions file published in the GitHub repository jim-schilling/splurge-ai-rules (3 stars, last pushed 1y ago), licensed MIT. It adds 3,215 tokens to every session, about $0.0129 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.

splurge-ai-rules copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
splurge-ai-rules copilot-instructions.mdjim-schilling/splurge-ai-rules	Instructions file	3	1y ago	MIT	A	3,215	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

splurge-ai-rules: Instructions file for GitHub Copilot