Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojonpx agentmods add skills/andreaswasita/copilot-agents-dojo/writing-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/skills/andreaswasita/copilot-agents-dojo/writing-skills)<a href="https://agentmods.dev/skills/andreaswasita/copilot-agents-dojo/writing-skills"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/writing-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/andreaswasita/copilot-agents-dojo/writing-skills"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/writing-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 141 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- high Anti-Refusal · line 159 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00017 | $0.01455 |
| Opus 5 | $0.00009 | $0.00727 |
| Sonnet 5 | $0.00003 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
writing-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 12d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Skills (meta) Skill
Walks the agent through producing a new SKILL.md that conforms to spec/copilot-skills-spec.md and passes scripts/verify.sh spec. Covers intent capture, folder layout, frontmatter, canonical body sections, and the test loop. Does NOT auto-register the new skill in skills.md — that is the regen script's job.
When to Use
- The user explicitly asks to create or amend a skill.
- A
tasks/lessons.mdpattern has ≥3 occurrences and should graduate to a skill. - The dojo curator (see
self-improvement) flags a candidate skill to formalize. - Team adapts the dojo for a new domain.
- NOT for one-off rules — those live in
tasks/lessons.mduntil they recur.
Prerequisites
spec/copilot-skills-spec.mdandtemplate/SKILL.mdexist (this skill is parasitic on them).- The
view,edit, andpowershellCopilot tools. scripts/verify.shavailable on the path (or git bash on Windows).- Decision recorded for which tier the new skill belongs in.
How to Run
1. Capture intent — what, when, what good looks like, what mistakes to prevent.
2. Pick the tier (core / practical / optional) and folder destination.
3. Copy `template/SKILL.md` to `<tier-dir>/<skill-name>/SKILL.md`.
4. Fill frontmatter; ≤60-char description with period; no marketing words.
5. Walk the canonical body sections in order.
6. Run `bash scripts/verify.sh spec` until the new skill is clean.
7. Hand off to the regen script (Phase 5.1) to update `skills.md`.
Quick Reference
| Tier | Folder | Loaded when |
|---|---|---|
| core | skills/ |
Always |
| practical | skills/ |
On trigger |
| optional | optional-skills/ |
Installed explicitly |
| Frontmatter key | Rule |
|---|---|
name |
Lowercase, hyphens, matches folder |
description |
≤60 chars, ends with period, no marketing words |
tier |
core | practical | optional |
category |
See spec §1.2 valid set |
created_by |
human or agent |
platforms |
Subset of [windows, macos, linux] |
author |
Name (@handle), human first |
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.
- 12d ago First seen · 164 lines · 17 tokens per session scan A 97f1b0353bb5
writing-skills is a skill published in the GitHub repository andreaswasita/copilot-agents-dojo (53 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 1,455 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
author-skill
Use when authoring a NEW rsc skill or editing an existing one — scoping it to one job, writing the description that decides whether it ever loads, splitting the body into references/, writing its evals, auditing it against the rubric. NOT building a product feature (that is specify) and NOT designing an agent loop…
continuous-learning
Use when a mistake, correction, or surprise taught the workspace something that must stick — a retro or postmortem, the same agent error corrected twice, a resolved bug's root cause, scattered notes-to-self — and route that lesson to the durable surface that fires next time. NOT a forward choice with alternatives…
orient
Always-on. The brújula: close every turn by situating the person — where they are, what just happened, why it mattered, and the next step as a question, never a dead end. Reads the accompaniment and technical dials from 02-DOCS and calibrates how much it explains, rewriting the dial when the user asks for more or…
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.