Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/thesethrose/copilot-skills/document-projectgit clone --depth 1 https://github.com/TheSethRose/Copilot-SkillsWrote 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/thesethrose/copilot-skills/document-project)<a href="https://agentmods.dev/instructions/thesethrose/copilot-skills/document-project"><img src="https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/document-project.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 | $0.02562 | $0.02562 |
| Opus 5 | $0.01281 | $0.01281 |
| Sonnet 5 | $0.00512 | $0.00512 |
| Haiku 4.5 | $0.00256 | $0.00256 |
Grade A, and why
Copilot-Skills document-project.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 3d 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 — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Project - Instructions
When working with documentation generation or when queries contain "document project", "generate docs", or "documentation", this context activates.
Core Purpose
Generate clear, structured markdown documentation for repositories. Analyze project structure, propose appropriate docs, and build a /docs folder with quality content.
Key Distinction: This skill generates PROJECT DOCUMENTATION (markdown files). For PDF/DOCX/PPTX manipulation, use /pdf-handling.
Default Behaviors
When user mentions "document project" or "generate docs"
- Suggest
/document-projectskill - Analyze current repository structure
- Detect project type, language, framework
- Propose appropriate documentation set
- Confirm before creating files
When user mentions "documentation" in general context
- Clarify intent: project docs or file manipulation?
- If project docs → use
/document-project - If file manipulation (PDF, etc.) → use
/pdf-handling
When analyzing a codebase
- Run
analyze_project.shto get project metadata - Check for existing documentation
- Respect
.gitignorepatterns - Detect open-source vs closed-source
- Propose template based on analysis
When generating documentation
- Always use
--dry-runfirst to preview - Show proposed file list to user
- Get confirmation before creating files
- Create
/docsfolder if needed - Generate markdown with proper formatting
- Validate output with
validate_docs.sh - Suggest linking from main README
Quality Guidelines
✅ Do
- Analyze before proposing documentation
- Use appropriate template (minimal, standard, open-source)
- Respect existing documentation (never overwrite without confirmation)
- Follow markdown best practices
- Include code examples in appropriate language
- Validate all generated markdown
- Respect
.gitignorepatterns - Use consistent tone and formatting
- Link documentation from main README
- Suggest conventional Git commit messages
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.
- 3d ago First seen · 469 lines · 2,562 tokens per session scan A 7f37bddc2255
Copilot-Skills document-project.instructions.md is an instructions file published in the GitHub repository TheSethRose/Copilot-Skills (3 stars, last pushed 8mo ago), licensed MIT. It adds 2,562 tokens to every session, about $0.0128 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
copilot copilot-instructions.md
Instructions for navikt/copilot, covering copilot instructions for navikt/copilot, repository overview, nav development standards, nav principles and nav tech stack.
copilot AGENTS.md
Instructions for navikt/copilot, covering agents.md for navikt/copilot, what this repo is, efficiency rule, standard commands and conventions.
Project Guidelines
VS Code extension project guidelines for GitHub Copilot Insights. Covers project shape, code style, VS Code extension rules, build and test, and repository discipline.
Repo Validation Workflow
Use when: changing, validating, testing, or reviewing this VS Code extension repository. Covers npm compile, lint, test harness, Electron test caveats, and build output.
sensei AGENTS.md
Instructions for spboyer/sensei, covering agents.md, repository structure, key conventions, skill.md format and skill body (markdown).
sensei copilot-instructions.md
Instructions for spboyer/sensei, covering copilot instructions, project context, skill authoring rules, token and scoring expectations and validation commands.