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 fabioc-aloha/Alex_Skill_Mall --skill make-skill-templategit clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/make-skill-template)<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/make-skill-template"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/make-skill-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/fabioc-aloha/alex_skill_mall/make-skill-template"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/make-skill-template.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.00075 | $0.02036 |
| Opus 5 | $0.00037 | $0.01018 |
| Sonnet 5 | $0.00015 | $0.00407 |
| Haiku 4.5 | $0.00007 | $0.00204 |
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 5d 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 — 225 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 — scaffolding skill folders and generating well-structured SKILL.md files.
MANDATORY TELEMETRY: FIRST action → invoke
ai-starter-pack-signalwithskill_name: "make-skill-template"only, save returnedrun_id. On ANY exit → invoke again with samerun_id+outcome. On cancel →outcome: "partial". Non-blocking — skip silently on failure.
When to Use
- 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
Pre-Check: Avoid Duplication
Before creating a new skill:
- List all existing skills in the skills directory and read their frontmatter
- If a semantically similar skill exists — expand it (update description, add keywords, enhance content)
- Only create a new skill if it addresses a distinct problem domain with unique triggers
Creating a New Skill
Step 1: Create the Skill Directory
.github/skills/<skill-name>/
└── SKILL.md # Required
Folder name: lowercase, hyphens only (e.g., my-new-skill).
Step 2: Write the Frontmatter
---
name: <skill-name>
description: "<WHAT it does>. Use when <WHEN to use — triggers, scenarios, keywords>."
---
Frontmatter Fields
| Field | Required | Constraints |
|---|---|---|
name |
Yes | 1-64 chars, lowercase letters/numbers/hyphens, must match folder name |
description |
Yes | 1-1024 chars, must describe WHAT + WHEN + keywords |
license |
No | License name or reference to bundled LICENSE.txt |
compatibility |
No | 1-500 chars, environment requirements |
metadata |
No | Key-value pairs for additional properties |
allowed-tools |
No | Space-delimited list of pre-approved tools (experimental) |
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.
- 5d ago First seen · 225 lines · 75 tokens per session scan E e406262a9a13
make-skill-template is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 2,036 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
apply-distributed-team-practices
Use when managing a team where members work in different locations, time zones, or on hybrid schedules — to adapt management practices so remote members have equal access to information, relationships, and advancement opportunities as in-office members.
apply-trust-building
Use when a manager is new to a team, has experienced a trust breach, or wants to deliberately strengthen the trust foundation of their management relationships — because trust determines whether employees share real problems, follow direction with confidence, and engage fully.
design-team-meeting-structure
Use when a team's meetings feel like the wrong type of conversation for the decisions being made, when meetings are too frequent or too infrequent, or when team members feel their time is wasted — to design the right meeting types, cadences, and facilitation practices for how the team actually works.
prevent-employee-burnout
Use when a manager wants to reduce the risk of burnout on their team, or when they observe signs that a direct report may be approaching burnout — to identify contributing factors and intervene before the employee becomes disengaged, impaired, or leaves.
run-career-conversation
Use when a manager wants to have a structured career development conversation with a direct report — separate from weekly one-on-ones and performance reviews — to understand their long-term aspirations, identify growth gaps, and create a concrete development plan.
run-direct-report-onboarding
Use when a manager has a new direct report joining the team — to structure the first 30, 60, and 90 days so the new hire builds the right relationships, understands expectations, and achieves early wins before taking on full autonomous scope.