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-skillsgit 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-skills)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/creating-skills"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-skills/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-skills"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-skills.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.00058 | $0.01111 |
| Opus 5 | $0.00029 | $0.00556 |
| Sonnet 5 | $0.00012 | $0.00222 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
creating-skills 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 13d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Copilot Skills
Use this skill when reusable know-how deserves a home of its own instead of living in prompts or chat history. It helps create skills that are discoverable, concise, and bundled with the right supporting assets.
When to Use
Use this skill when the user asks for things like:
- "create a new Copilot skill"
- "package this workflow as a reusable skill"
- "turn our team process into a
SKILL.md" - "add templates and examples to a skill folder"
- "fix a skill that is too long, vague, or hard to trigger"
Typical scenarios:
- creating a brand-new skill folder
- refactoring a bloated
SKILL.mdinto a leaner body plus resource files - improving discovery quality through better naming and descriptions
- preparing a public-ready skill with templates, examples, and a validation checklist
Outcome Standard
A strong skill contribution usually includes:
- a name that clearly describes the activity the skill supports
- a description that explains both what the skill does and when to use it
- a
SKILL.mdbody that teaches a workflow, not a persona - supporting resources that are loaded on demand instead of bloating the main file
- a clear definition of done so the agent knows when to stop
Skill Design Rules
- Activity, not topic - name the skill after the task it performs, not the subject area alone.
- Trigger-friendly descriptions - include realistic user phrases and contexts.
- Progressive disclosure - keep the skill body focused; move templates, examples, and detailed checklists into
resources/. - One coherent capability - avoid turning one skill into a junk drawer of unrelated workflows.
- Workflow first - the main body should help the agent execute the task step by step.
Workflow
Phase 0: Frame the capability
Clarify or infer:
- the exact task the skill should help perform
- the signals that should trigger the skill
- the expected output or artifact bundle
- what makes the skill distinct from nearby skills in the repository
What ships with it
3 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.
- 13d ago First seen · 135 lines · 58 tokens per session scan A 197bbaaae2ed
creating-skills is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 17d ago), licensed MIT. It adds 58 tokens to every session and 1,111 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.