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-hooksgit 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-hooks)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/creating-hooks"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-hooks/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-hooks"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/creating-hooks.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.00053 | $0.00949 |
| Opus 5.5 | $0.00021 | $0.00380 |
| Sonnet 5.5 | $0.00011 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
creating-hooks 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 1mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Copilot Hooks
Use this skill when the right answer is not more advice, but deterministic behavior at a specific lifecycle point. It helps design hooks that are safe, documented, and understandable.
When to Use
Use this skill when the user asks for things like:
- "create a Copilot hook for this policy"
- "block dangerous commands before they run"
- "log or validate tool usage automatically"
- "add a reusable hook pack with docs and scripts"
- "turn this manual guardrail into a hook"
Typical scenarios:
- pre-tool checks for risky shell commands
- post-tool validation or formatting triggers
- audit or observability hooks for shared environments
- installing a documented hook bundle for reuse across workspaces
Outcome Standard
A strong hook contribution usually includes:
- the right lifecycle event and the smallest useful behavior
- explicit safety defaults and clear denial or warning messages
- a documented
hooks.jsonconfiguration - cross-platform script guidance when Windows and Bash users both matter
- a README or pack that explains purpose, setup, and limitations
Hook Design Rules
- Start with observe or warn - block only when the policy is stable and the failure message is clear.
- Keep hooks fast - long-running hooks become friction generators instead of safeguards.
- Be explicit on denial - if a hook blocks work, explain exactly why and what to do instead.
- Separate policy from docs - the script enforces behavior; the README explains it.
- Prefer deterministic checks - hooks should not depend on fuzzy interpretation when avoidable.
Workflow
Phase 0: Decide whether a hook is the right primitive
Use a hook when deterministic automation is needed at a lifecycle event. If the need is guidance only, use instructions. If the need is a reusable workflow, use a skill. If the need is a user-started task, use a prompt.
Phase 1: Choose the lifecycle event
Clarify or infer:
- what event should trigger the hook
- whether the behavior is observe, warn, mutate, or deny
- how quickly the hook must complete
- whether it needs cross-platform script support
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.
- 1mo ago First seen · 120 lines · 53 tokens per session scan A 93cff0852730
creating-hooks is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (118 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 949 once invoked, about $0.0002 per session on Opus 5.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.
stripe-backend
Centralized LLM prompt instructions for Copilot and Cursor, including scripts to convert and sync rules for Python, React, Shell, and TypeScript. Designed for rapid reuse and contribution across projects.
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.