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/s977043/plangate/skill-creatornpx skills add s977043/PlanGate --skill skill-creatorgit clone --depth 1 https://github.com/s977043/PlanGateWrote 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/s977043/plangate/skill-creator)<a href="https://agentmods.dev/skills/s977043/plangate/skill-creator"><img src="https://agentmods.dev/badge/skills/s977043/plangate/skill-creator.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.00103 | $0.01847 |
| Opus 5 | $0.00051 | $0.00924 |
| Sonnet 5 | $0.00021 | $0.00369 |
| Haiku 4.5 | $0.00010 | $0.00185 |
Grade A, and why
skill-creator 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.
This is a copy
89% identical to skill-creator — 142 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Create a new skill only after the use case is concrete enough.
Your job is to:
- identify the smallest useful responsibility
- define when the skill should trigger
- choose safe frontmatter defaults
- draft a minimal but strong
SKILL.md - propose supporting files only when they add clear value
- define an initial eval set
Safety constraints
Write output files only to .agents/skills/ unless the user explicitly specifies a different path.
Do not modify existing skills without user confirmation.
Note: this skill does not set disable-model-invocation: true because file creation is its primary purpose, not an incidental side effect. The settings.json deny list and user confirmation prompts provide sufficient guardrails.
Core rule
Do not create a broad or fuzzy skill.
Prefer:
- one responsibility
- one primary workflow
- one clear success condition
If the requested scope is too broad, split it into multiple skills.
Phase 0: Gate（ヒアリング）
Before drafting, confirm the following through interactive dialogue. Ask naturally — do not dump all questions at once.
- ゴール: このスキルで何を達成したいか？
- ユースケース: 具体的な利用シーン（2〜3個）
- カテゴリ判定: 以下のどれに最も近いか？
- Category 1: ドキュメント・アセット生成（テンプレート型）
- Category 2: ワークフロー自動化（ステップ型）
- Category 3: MCP連携強化（ツール活用型）
- トリガー: ユーザーがどんな言葉でこのスキルを呼び出すか？（日本語・英語両方）
- 入力: スキルが受け取る情報は何か？
- 出力: スキルが生成・実行する成果物は何か？
- allowed tools: 必要なツール
- auto vs manual: 自動起動か手動起動か
- 品質基準: 成功をどう判定するか？
- definition of done
If any item is unclear:
- ask the minimum focused questions, or
- inspect available files first if the answer can be found without asking
Do not draft the full skill until the gate passes.
Phase 1: Skill boundary design
Produce a short working summary with:
- skill name candidate
- single responsibility
- in-scope tasks
- out-of-scope tasks
- likely trigger language
- risk level
- pattern selection:
| パターン | 用途 |
|---|---|
| Sequential Workflow | 順序固定の多段階プロセス |
| Multi-MCP Coordination | 複数サービスを横断する連携 |
| Iterative Refinement | 品質を反復改善するループ |
| Context-aware Selection | 状況に応じてツール・手法を切り替え |
| Domain Intelligence | 専門知識を判断ロジックに埋め込み |
What ships with it
4 files 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.
- 5d ago First seen · 232 lines · 103 tokens per session scan A 3312d54c893d
skill-creator is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed 5d ago), licensed MIT. It adds 103 tokens to every session and 1,847 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to skill-creator, differing in 142 lines, and is treated as a copy.
Other skills, from other repositories
skill-maintenance
Automated skill maintenance tool (v6 — Unified Registry + Snapshots). Full scan: [Orphan] migrate misplaced skills from category dirs OR standalone skills/<name>/ to auto-generated/, [Sync] auto-generated/ vs registry lifecycle diff (new/deleted/revived + description auto-sync via lifecycle field), [Reg]…
extract
Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.