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 paultyng/skill-issue --skill create-skillgit clone --depth 1 https://github.com/paultyng/skill-issueWrote 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/paultyng/skill-issue/create-skill)<a href="https://agentmods.dev/skills/paultyng/skill-issue/create-skill"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/create-skill/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/paultyng/skill-issue/create-skill"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/create-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00036 | $0.02154 |
| Opus 5.5 | $0.00014 | $0.00862 |
| Sonnet 5.5 | $0.00007 | $0.00431 |
| Haiku 4.5 | $0.00004 | $0.00215 |
Grade A, and why
create-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 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Skill
Skill Types
Categorize before writing -- this determines structure, degrees of freedom, and testing approach:
- Technique: concrete method with steps (e.g. condition-based-waiting)
- Pattern: mental model / way of thinking (e.g. flatten-with-flags)
- Reference: API docs, syntax guides, tool documentation
- Workflow: multi-step process with decision points (e.g. ship-it)
Requirements Gathering
Infer from conversation context when possible. If clarification is needed, use AskQuestion (or ask conversationally if unavailable). Capture:
- Purpose and scope: what specific task or workflow
- Storage location: personal (
~/.cursor/skills/) or project (.cursor/skills/) - Trigger scenarios: when should the agent apply this skill
- Domain knowledge: what the agent wouldn't already know
- Output format: templates, styles, or conventions required
- Existing patterns: examples or conventions to follow
Design
Name
- Lowercase letters, numbers, hyphens only. Max 64 chars
- Prefer verb-first or gerund form:
create-skill>skill-creation,analyze-sessions>session-analysis - Name by what you DO or core insight, not generic labels
- Avoid:
helper,utils,tools,misc
Description (CSO-Critical)
The description determines whether the agent loads this skill. Max 1024 chars, third person.
Start with "Use when..." -- describe ONLY triggering conditions (symptoms, situations, contexts).
NEVER summarize the skill's workflow or process. Testing shows agents follow descriptions as shortcuts, skipping the full skill body. A description saying "does X then Y" causes agents to do exactly X then Y without reading the actual detailed instructions.
Include concrete triggers: error messages, symptoms, tool names, synonyms.
# BAD: workflow summary -- agent will shortcut to this
description: Analyzes code diffs, generates commit messages, and pushes to remote.
# BAD: too vague
description: Helps with documents.
# GOOD: triggering conditions only
description: Use when reviewing pull requests, examining code changes, or when asked for a code review.
# GOOD: specific triggers with keywords
description: Use when tests have race conditions, timing dependencies, or pass/fail inconsistently.
What ships with it
1 file 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 · 224 lines · 36 tokens per session scan A bfc20ec4b7b0
create-skill is a skill published in the GitHub repository paultyng/skill-issue (8 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 2,154 once invoked, about $0.0001 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-31.
Other skills, from other repositories
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
verify
Fact-check claims encountered during reading — dates, names, events, citations. Use when encountering historical facts or disputed claims.
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter…
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.
design-improvement
WHAT - Browser-grounded iterative design improvement. Consumes design-assessment findings, defines direction, prioritizes safe vs ambiguous changes, implements within existing design system, runs app, captures rendered evidence via browser, reviews and iterates. Reuses evidence model — no new scoring framework.
codeql
CodeQL operational workflow — discover/config, run/inspect, triage SARIF findings (rule/query ID, source→sink, evidence), remediate, re-validate. Distinguishes broad MegaLinter linting from semantic security analysis.