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 andreaswasita/copilot-agents-dojo --skill templategit clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojoWrote 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/andreaswasita/copilot-agents-dojo/template)<a href="https://agentmods.dev/skills/andreaswasita/copilot-agents-dojo/template"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/template/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/andreaswasita/copilot-agents-dojo/template"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/template.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.00012 | $0.00927 |
| Opus 5 | $0.00006 | $0.00464 |
| Sonnet 5 | $0.00002 | $0.00185 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
template-skill 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template Skill
Two to three sentences stating what this skill does AND what it deliberately does NOT do. The "does not" half is as important as the "does" half — it prevents over-triggering on adjacent tasks.
When to Use
Specific triggers, keywords, and contexts that should activate the skill. Be slightly pushy — agents undertrigger more often than they overtrigger.
- Trigger condition 1 (concrete situation, not abstract)
- Trigger condition 2
- Trigger condition 3 (include negative triggers if helpful: "but NOT when…")
Prerequisites
What must be true before the skill can run.
- Tool / MCP server availability
- Required env vars or config keys
- Repo state (e.g. clean working tree, on a feature branch)
If a prerequisite is missing, the skill must fail loudly — never degrade silently.
How to Run
One-screen overview of the canonical happy path. If the skill ships a script, show the command:
scripts/example.sh --flag value
Quick Reference
| Action | Command / Tool | Notes |
|---|---|---|
| Common op 1 | view path |
Use the Copilot view tool, not shell cat. |
| Common op 2 | grep pattern |
Use the Copilot grep tool, not shell grep/rg. |
| Common op 3 | scripts/example.sh |
Ships with the skill. |
The agent should be able to act from this table alone for routine cases.
Procedure
Step-by-step detailed workflow. This is where the depth lives.
Step 1: Assess
What the agent checks before acting.
Step 2: Act
The actual work. Reference real Copilot tools in backticks (view, edit, grep, glob, powershell, web_fetch, task). Do NOT instruct the agent to call bare shell utilities (cat, sed, find) that have a Copilot wrapper.
Step 3: Confirm
Intermediate verification before moving on.
Pitfalls
Imperative "DO NOT" register of failure modes this skill prevents.
- DO NOT [common mistake 1] — [why it bites].
- DO NOT [common mistake 2] — [why it bites].
- DO NOT [common mistake 3] — [why it bites].
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 · 119 lines · 12 tokens per session scan A cf06330b6d18
template-skill is a skill published in the GitHub repository andreaswasita/copilot-agents-dojo (51 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 927 once invoked, about $0.0001 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
decision-ledger
A session record for tracking unresolved decisions and drafting them into `.governance/claims/` when they are settled. It preserves both the decision and the reason behind it.
governance-bootstrap
A guided checklist for creating a project's governance system from scratch when no governance exists.
session-grounding
A session-start procedure for checking the current facts, scope, and work track in a governed project before taking action.
truth-first
A set of rules for writing technical conclusions and performing irreversible or state-changing operations. It requires evidence tied to file and line locations and restricts unsupported claims.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.