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 skills add jaktestowac/awesome-copilot-for-testers --skill creating-instructionsgit clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/skills/jaktestowac/awesome-copilot-for-testers/creating-instructions)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/creating-instructions"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-instructions/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/creating-instructions"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01200 |
| Opus 5 | $0.00026 | $0.00600 |
| Sonnet 5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
creating-instructions 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 9d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Copilot Instructions
Use this skill when the goal is to package stable rules for GitHub Copilot instead of writing one-off guidance in chat. It helps turn repository conventions into clean instruction files that are easy to install, reason about, and maintain.
When to Use
Use this skill when the user asks for things like:
- "create a repo-wide Copilot instruction file"
- "write a
.instructions.mdfile for these tests" - "choose the right
applyTopattern" - "turn our coding rules into installable instructions"
- "fix an instruction file that is too broad or too vague"
Typical scenarios:
- first-time setup of
copilot-instructions.md - adding targeted guidance for a folder, language, or test type
- splitting an overgrown instruction file into smaller units
- preparing public examples for a team repository or a shared collection
What Good Looks Like
A strong instruction contribution usually includes:
- the right instruction type for the job: repo-wide or scoped
- a narrow, predictable scope
- short declarative rules with a reason when the rule is not obvious
- examples only where they materially improve compliance
- no workflow logic, no agent personality, and no prompt-specific scripting
Instruction Design Rules
- Rules over essays - prefer short, stable guidance that survives multiple tasks.
- Scope first - the
applyTopattern is part of the design, not an afterthought. - Reason when needed - if a rule is surprising, explain the consequence in the same bullet.
- Examples beat abstraction - include a preferred and avoided example for tricky patterns.
- Context is expensive - avoid loading broad instructions that repeat what tools already enforce.
Workflow
Phase 0: Frame the request
Clarify or infer:
- whether the user needs repo-wide guidance or scoped instructions
- who will install the file: one user, a team, or a public collection
- which files or folders must be affected
- what conventions are stable enough to encode as rules
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 142 lines · 51 tokens per session scan A cdafe2536c1b
creating-instructions is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 13d ago), licensed MIT. It adds 51 tokens to every session and 1,200 once invoked, about $0.0003 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 skills, from other repositories
fastapi_stripe
A Stripe Checkout implementation takes four steps.
standalone-python-scripts
Skill "standalone-python-scripts" from iloveitaly/llm-ide-rules, covering standalone python scripts, /// script, requires-python = ">=3.13", dependencies = [] and ///.
secrets
Here's how environment variables are managed in this application.
fix-tests
Focus on all unit + command tests (pytest --exclude tests/integration). Make sure they pass and fix errors. If you run into anything very odd: stop, and let me know. Mutate test code first and let me know if you think you should update application code.
plan-only
As this point, I only want to talk about the plan. How would you do this? What would you refactor to make this design clean? You are an expert software engineer and I want you to think hard about how to plan this project out.
dev-in-browser
Use your browser to view https://verso.localhost which is tied to livereload dev server which is already running. You can inspect that page (including taking screenshots!) to validate that your changes fixed the issue.