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.
curl -O https://raw.githubusercontent.com/jim-schilling/splurge-ai-rules/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/jim-schilling/splurge-ai-rulesWrote 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/jim-schilling/splurge-ai-rules/copilot-instructions)<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="Measured on agentmods" 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.03215 | $0.03215 |
| Opus 5 | $0.01607 | $0.01607 |
| Sonnet 5 | $0.00643 | $0.00643 |
| Haiku 4.5 | $0.00321 | $0.00321 |
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 8d 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.
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").
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.
- 8d ago First seen · 238 lines · 3,215 tokens per session scan A 6bbeb1b79259
splurge-ai-rules copilot-instructions.md is an instructions file published in the GitHub repository jim-schilling/splurge-ai-rules (3 stars, last pushed 11mo ago), licensed MIT. It adds 3,215 tokens to every session, about $0.0161 per session on Opus 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.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.