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 agentmods add skills/boshi-xixixi/traeskill/make-skill-templatenpx skills add boshi-xixixi/TraeSkill --skill make-skill-templategit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/make-skill-template)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/make-skill-template"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/make-skill-template.svg" alt="Measured on agentmods" 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.00075 | $0.01227 |
| Opus 5 | $0.00037 | $0.00613 |
| Sonnet 5 | $0.00015 | $0.00245 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
make-skill-template 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 2d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- make-skill-template — 100% identical, 0 lines differ
- make-skill-template — 100% identical, 52 lines differ
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make Skill Template
A meta-skill for creating new Agent Skills. Use this skill when you need to scaffold a new skill folder, generate a SKILL.md file, or help users understand the Agent Skills specification.
When to Use This Skill
- User asks to "create a skill", "make a new skill", or "scaffold a skill"
- User wants to add a specialized capability to their GitHub Copilot setup
- User needs help structuring a skill with bundled resources
- User wants to duplicate this template as a starting point
Prerequisites
- Understanding of what the skill should accomplish
- A clear, keyword-rich description of capabilities and triggers
- Knowledge of any bundled resources needed (scripts, references, assets, templates)
Creating a New Skill
Step 1: Create the Skill Directory
Create a new folder with a lowercase, hyphenated name:
skills/<skill-name>/
└── SKILL.md # Required
Step 2: Generate SKILL.md with Frontmatter
Every skill requires YAML frontmatter with name and description:
---
name: <skill-name>
description: '<What it does>. Use when <specific triggers, scenarios, keywords users might say>.'
---
Frontmatter Field Requirements
| Field | Required | Constraints |
|---|---|---|
name |
Yes | 1-64 chars, lowercase letters/numbers/hyphens only, must match folder name |
description |
Yes | 1-1024 chars, must describe WHAT it does AND WHEN to use it |
license |
No | License name or reference to bundled LICENSE.txt |
compatibility |
No | 1-500 chars, environment requirements if needed |
metadata |
No | Key-value pairs for additional properties |
allowed-tools |
No | Space-delimited list of pre-approved tools (experimental) |
Description Best Practices
CRITICAL: The description is the PRIMARY mechanism for automatic skill discovery. Include:
- WHAT the skill does (capabilities)
- WHEN to use it (triggers, scenarios, file types)
- Keywords users might mention in prompts
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.
- 2d ago First seen · 148 lines · 75 tokens per session scan A 8f2d681b7cda
make-skill-template is a skill published in the GitHub repository boshi-xixixi/TraeSkill (261 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,227 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
<skill-name>
当用户 时使用。典型信号：用户说" "、 。涉及关键词： 、 。只写"何时触发"，不写工作流；第三人称、中文。上限 1024 字符.
spec-writing
Skill "spec-writing" from Lion-1209/Lion-Skills, covering spec writing, 概述, 何时使用, 核心内容 and 先判断时机：spec 之前还有没有重大未知.
onboarding-unknown-codebase
需快速上手陌生代码库、理解项目结构时。.
commit-message
把一团 diff 提炼成规范、可追溯的提交信息。核心：一条提交说清"做了什么"和"为什么"，让未来的自己（和同事）能从提交历史里读懂项目演进。.
clarifying-questions
需求模糊、含隐藏假设或 X-Y problem，需先澄清再动手时。.
debugging
用科学方法定位 bug 的根因，而不是凭直觉乱改碰运气。核心：调试是观察 → 假设 → 设计实验验证 → 缩小范围 → 定位根因的循环，每一步都有依据。改到"不报错"不算修好——那可能只是把症状盖住了，根因还在。.