Borrowing it
Nothing to install: this file belongs to JimmyPaolini/codebase. 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/JimmyPaolini/codebase/main/.github/instructions/prompt.instructions.mdgit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/jimmypaolini/codebase/prompt)<a href="https://agentmods.dev/instructions/jimmypaolini/codebase/prompt"><img src="https://agentmods.dev/badge/instructions/jimmypaolini/codebase/prompt.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.01216 | $0.01216 |
| Opus 5 | $0.00608 | $0.00608 |
| Sonnet 5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
codebase prompt.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 4d 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.
This is a copy
100% identical to custom_github_copilot_agent_builder prompt.instructions.md — 37 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Prompt Files Guidelines
Instructions for creating effective and maintainable prompt files that guide GitHub Copilot in delivering consistent, high-quality outcomes across any repository.
Scope and Principles
- Target audience: maintainers and contributors authoring reusable prompts for Copilot Chat.
- Goals: predictable behavior, clear expectations, minimal permissions, and portability across repositories.
- Primary references: VS Code documentation on prompt files and organization-specific conventions.
Frontmatter Requirements
Every prompt file should include YAML frontmatter with the following fields:
Required/Recommended Fields
| Field | Required | Description |
|---|---|---|
description |
Recommended | A short description of the prompt (single sentence, actionable outcome) |
name |
Optional | The name shown after typing / in chat. Defaults to filename if not specified |
agent |
Recommended | The agent to use: ask, edit, agent, or a custom agent name. Defaults to current agent |
model |
Optional | The language model to use. Defaults to the currently selected model |
tools |
Optional | List of tool/tool set names available for this prompt |
argument-hint |
Optional | Hint text shown in chat input to guide user interaction |
Guidelines
- Use consistent quoting (single quotes recommended) and keep one field per line for readability and version control clarity
- If
toolsare specified and the current agent isaskoredit, the default agent becomesagent - Preserve any additional metadata (
language,tags,visibility, etc.) required by your organization
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.
- 4d ago First seen · 100 lines · 1,216 tokens per session scan A b7a2e08449a5
codebase prompt.instructions.md is an instructions file published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed today), licensed MIT. It adds 1,216 tokens to every session, about $0.0061 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to custom_github_copilot_agent_builder prompt.instructions.md, differing in 37 lines, and is treated as a copy.
Other instructions, from other repositories
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).
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.
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 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).
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.