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 usefulmove/enso --skill create-skillgit clone --depth 1 https://github.com/usefulmove/ensoWrote 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/usefulmove/enso/create-skill)<a href="https://agentmods.dev/skills/usefulmove/enso/create-skill"><img src="https://agentmods.dev/badge/skills/usefulmove/enso/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/usefulmove/enso/create-skill"><img src="https://agentmods.dev/badge/skills/usefulmove/enso/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.00053 | $0.01140 |
| Opus 5.5 | $0.00021 | $0.00456 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,140 once invoked, about $0.0002 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
harness
A meta-skill for designing and maintaining a project harness: a coordinated set of specialist agents, skills, and project instructions. It defines their roles, connects them to the project, and updates the setup as the work changes.
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisQuarter
Resolve "thisQuarter" to a concrete ISO date range relative to your run time — this quarter so far (quarter start → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a quarter-to-date task (QTD…
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…
evolve
A workflow for improving an existing setup that guides coding agents. It collects results and feedback, compares the current setup with its starting version, and records useful changes.
md-fetch-summarize
Fetch a URL and return a concise markdown summary of its content. Read-only: no files are written; the summary is returned as output only. Use when asked to "fetch and summarize", "summarize this URL", "what does this page say", or "get the content of ". Proactively suggest when the user pastes a URL and asks what it…