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/context7git 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/context7)<a href="https://agentmods.dev/instructions/thesethrose/copilot-skills/context7"><img src="https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/context7.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.02321 | $0.02321 |
| Opus 5 | $0.01161 | $0.01161 |
| Sonnet 5 | $0.00464 | $0.00464 |
| Haiku 4.5 | $0.00232 | $0.00232 |
Grade A, and why
Copilot-Skills context7.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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context7 - Automatic Context Instructions
Related Prompt: /context7
Related Skill: .github/copilot-skills/documentation/context7/
Triggers: context7, up-to-date docs, latest documentation, library documentation, resolve library, get docs
Context: Up-to-Date Library Documentation
When working with library documentation or when user queries mention getting current docs, this context is automatically activated.
Core Principles
Always Use Current Documentation
- Never rely on outdated docs from training data
- Always check Context7 first for library information
- Verify versions - libraries change rapidly
- Trust scores matter - prefer 7-10 range
Progressive Documentation Retrieval
- Start broad - Resolve library ID first
- Get specific - Request docs with focused topics
- Iterate - Refine topic if results aren't helpful
- Cache - Remember frequently used patterns
Default Behaviors
When user mentions "need docs for {library}"
- Suggest
/context7skill prompt - Call
resolve-library-idwith library name - Show top 3-5 matches with trust scores
- Ask user to confirm which library
- Fetch docs with relevant topic
When user mentions "latest {library} features"
- Resolve library ID
- Check for version information
- Get docs with topic "new features" or "changelog"
- Highlight recent updates
- Compare with older versions if available
When enhancing a skill
- Identify which libraries the skill covers
- Resolve IDs for each library
- Fetch current documentation
- Update
patterns.mdwith latest examples - Refresh
reference.mdwith current APIs - Note the update date and Context7 source
When user asks "which library should I use"
- Resolve multiple candidate libraries
- Compare trust scores
- Compare snippet counts (coverage indicator)
- Fetch brief docs for top candidates
- Present comparison table
- Recommend based on use case + trust + coverage
Quality Guidelines
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 · 352 lines · 2,321 tokens per session scan A 73d6a2364ed0
Copilot-Skills context7.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,321 tokens to every session, about $0.0116 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
Copilot instructions for navikt/copilot, covering copilot instructions for navikt/copilot, repository overview, nav development standards, nav principles and nav tech stack.
copilot AGENTS.md
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).
SonarCloud-Skill-Agent-Guidance
Repository guidance for the SonarCloud/SonarQube findings management skill.