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/usefulmove/enso/create-skillnpx skills add usefulmove/enso --skill create-skillgit clone --depth 1 https://github.com/usefulmove/ensoWhat 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 | $0.00053 | $0.01140 |
| Opus 5 | $0.00026 | $0.00570 |
| Sonnet 5 | $0.00011 | $0.00228 |
| Haiku 4.5 | $0.00005 | $0.00114 |
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 yesterday.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Load this skill when:
- A recurring task has no existing skill
- A complex procedure needs to be captured for reuse
- A capability gap is identified during a session
- The user asks to create or formalize a skill
Spec Reference
The authoritative opencode skill specification lives at: https://opencode.ai/docs/skills/
Consult it for current frontmatter fields, name validation rules, length limits, and permission configuration. The summary below reflects current best practice — when in doubt, the spec takes precedence.
What Makes a Good Skill
A skill is a reusable, loadable workflow — not a one-off script. It should:
- Solve a specific, recurring problem
- Be general enough to apply across projects
- Be concise enough to load without bloating the context window
- Tell the agent when to use it, not just how
A skill is not:
- A project-specific script (put that in
docs/skills/<project>/orscripts/) - A reference document (put that in
docs/reference/) - A story or task (put that in
docs/stories/)
Skill Structure
docs/skills/<skill-name>/
SKILL.md # required — the skill itself
scripts/ # optional — helper scripts
references/ # optional — reference material
assets/ # optional — templates, examples
SKILL.md is the only required file. Add supporting directories only when they add real value.
SKILL.md Format
---
name: <skill-name>
description: <One sentence. What it does and when to use it. This is what agents read to decide whether to load the skill.>
license: MIT
compatibility: opencode
---
## When to Use
<2-5 bullet points. Specific triggers. When should an agent load this skill?>
---
## <Workflow or Concept Section>
<The actual skill content. Structure depends on the skill type:>
- Procedural skills: numbered steps, phases, checklists
- Reference skills: tables, examples, decision trees
- Hybrid: both
## Checklist (if applicable)
- [ ] <Verifiable completion criteria>
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.
- yesterday First seen · 132 lines · 53 tokens per session scan A a663cc556018
create-skill is a skill published in the GitHub repository usefulmove/enso (2 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 1,140 once invoked, about $0.0003 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-31.
Other skills, from other repositories
git-conventions
The Lossless Group's git commit message conventions — structured headers with action verbs and effort groupings, paragraph-spaced bodies that explain impact before implementation, and "Also included" riders for minor changes. Use when writing commit messages, reviewing commits, or when the user mentions "commit…
stitch-loop
Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern.
write-skills
Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill, improving trigger descriptions, or deciding what belongs in a skill versus references, scripts, assets, or ordinary docs.
harness
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때, (5) '하네스 점검', '하네스 감사', '하네스 현황', '에이전트/스킬 동기화' 등 기존 하네스 운영/유지보수 요청 시 사용.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.
dsh-doc-standards
Use when writing, moving, reviewing, or auditing documentation in the deepseek-harness repo — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a verify-doc-budgets failure, or requests like "improve the docs", "audit the docs", "where…