Borrowing it
Nothing to install: this file belongs to tao-hpu/nano-spec. 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/tao-hpu/nano-spec/master/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/tao-hpu/nano-specWrote 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/tao-hpu/nano-spec/copilot-instructions)<a href="https://agentmods.dev/instructions/tao-hpu/nano-spec/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/tao-hpu/nano-spec/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.00754 | $0.00754 |
| Opus 5 | $0.00377 | $0.00377 |
| Sonnet 5 | $0.00151 | $0.00151 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
nano-spec 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 7d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nano-spec Instructions for GitHub Copilot
What is nano-spec?
A lightweight task specification methodology using 4 documents:
- README.md (Context)
- todo.md (Plan + Acceptance Criteria)
- doc.md (Technical Decisions)
- log.md (Progress Journal)
When to Create a nano-spec
- User asks to "create a spec for..."
- User asks to "plan a task..."
- User describes a multi-step development task
- User wants to document a technical decision
How to Generate
Step 1: Understand the Task
Ask clarifying questions if the description is vague:
- What's the end goal?
- What's explicitly NOT in scope?
- Are there dependencies on other work?
Step 2: Create Files
Generate in tasks/{task-name}/ or project root, following the exact structure below:
README.md
# {Task Name}
## Background
{Why does this task exist? What problem are we solving?}
## Goals
- {Goal 1}
- {Goal 2}
## Scope
### In Scope
- {What's included}
### Out of Scope
- {What's NOT included - be explicit}
## Dependencies
- [ ] {Dependency 1 - e.g., another task, external API, team decision}
## Resources
- {Link to related docs}
- {Link to external references}
todo.md
# TODO
## Research
- [ ] {Research item 1}
- [ ] {Research item 2}
## Implementation
- [ ] {Task 1}
- [ ] {Task 2}
- [ ] {Task 3}
## Verification
- [ ] {Verification step}
---
## Acceptance Criteria
### Must Have
- [ ] {Criterion 1 - specific, measurable}
- [ ] {Criterion 2}
### Nice to Have
- [ ] {Optional criterion}
### Out of Scope
- {Explicitly NOT part of this task's acceptance}
doc.md
# {Task Name} - Technical Document
## Summary
{One paragraph summary of the solution/outcome}
## Key Decisions
### Decision 1: {Title}
- **Options considered**: A, B, C
- **Chosen**: B
- **Rationale**: {Why B?}
## Technical Details
### Architecture / Data Flow
{Diagram using ASCII or describe the flow}
### Interfaces / Schema
```typescript
// Key interfaces if applicable
interface Example {
id: string;
name: string;
}
Implementation Notes
- {Note 1}
- {Note 2}
Open Questions
- {Unresolved question 1}
- {Unresolved question 2}
References
- {Link 1}
- {Link 2}
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.
- 7d ago First seen · 164 lines · 754 tokens per session scan A 1f9fd5c75b2f
nano-spec copilot-instructions.md is an instructions file published in the GitHub repository tao-hpu/nano-spec (46 stars, last pushed 7mo ago), licensed MIT. It adds 754 tokens to every session, about $0.0038 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-30.
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.