agent-bank: Skill for OpenCode

.opencode/skill/skill-authoring/SKILL.md

skill-authoring is a skill for OpenCode from different-ai/agent-bank. It costs 14 tokens per session (491 once invoked), scanned A, original, MIT.

A workflow for creating and registering reusable OpenCode skills, which are documented instructions for coding-agent tasks. It covers the required folder, file format, naming, and discovery checks.

In plain words
What is it for?
Use it to create a skill under the supported project or global locations, write its documentation, validate its name and frontmatter, and check that OpenCode lists it.
Why use it?
It reduces guesswork when adding a new skill or updating its metadata. It also helps ensure the skill can be found and used by OpenCode.

Skill for OpenCode

Written for OpenCode: installed under .opencode/. Also seen: reads .claude/ paths; mentions OpenCode.

This is different-ai/agent-bank's own configuration. It tells OpenCode how to work on agent-bank itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agent-bank configures →

Reuse

Borrowing it

Nothing to install: this file belongs to different-ai/agent-bank. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/different-ai/agent-bank/main/.opencode/skill/skill-authoring/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/different-ai/agent-bank

Made for: OpenCode.

Wrote 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.

agentmods badge for skill-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/different-ai/agent-bank/skill-authoring/github.svg)](https://agentmods.dev/skills/different-ai/agent-bank/skill-authoring)
Your own site
<a href="https://agentmods.dev/skills/different-ai/agent-bank/skill-authoring"><img src="https://agentmods.dev/badge/skills/different-ai/agent-bank/skill-authoring/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.

agentmods 80×15 button for skill-authoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/different-ai/agent-bank/skill-authoring"><img src="https://agentmods.dev/badge/skills/different-ai/agent-bank/skill-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 491 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00491
Opus 5.5 $0.00006 $0.00196
Sonnet 5.5 $0.00003 $0.00098
Haiku 4.5 $0.00001 $0.00049

Measured 1mo ago against content hash e5f940039992, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skill-authoring 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.

.opencode/skill/skill-authoring/SKILL.md · 65 lines

What it actually says

What I do

  • Define the steps and checks for adding a new OpenCode skill
  • Ensure the skill is discoverable by the skill tool
  • Validate naming, frontmatter, and placement rules

When to use

  • Adding a new reusable workflow or playbook as a skill
  • Updating skill metadata to meet OpenCode discovery requirements

Workflow

  1. Pick a skill name that matches ^[a-z0-9]+(-[a-z0-9]+)*$ and is 1–64 chars.
  2. Create .opencode/skill/<name>/SKILL.md and ensure the folder matches the name.
  3. Add YAML frontmatter with name and description (optional: license, compatibility, metadata).
  4. Write the body with clear sections (Purpose/What I do, When to use, Workflow, Completion criteria).
  5. Confirm discovery: run OpenCode in the repo and check skill tool list.
  6. If permissions block it, update opencode.json with permission.skill rules.

Placement rules (from opencode.ai docs)

  • Project: .opencode/skill/<name>/SKILL.md
  • Project (Claude compatible): .claude/skills/<name>/SKILL.md
  • Global: ~/.config/opencode/skill/<name>/SKILL.md
  • Global (Claude compatible): ~/.claude/skills/<name>/SKILL.md

Validation checklist

  • SKILL.md is all caps and contains YAML frontmatter
  • name matches folder name
  • description is 1–1024 characters
  • No duplicate skill names in the repo

Example

---
name: git-release
description: Create consistent releases and changelogs
compatibility: opencode
---

## What I do

- Draft release notes from merged PRs
- Propose a version bump
- Provide a `gh release create` command

Completion criteria

  • Skill appears in skill tool list
  • skill({ name }) loads without errors
  • Instructions are clear enough to execute without extra context
Changes

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.

  1. 1mo ago First seen · 65 lines · 14 tokens per session scan A e5f940039992

Subscribe to this mod's changes

skill-authoring is a skill published in the GitHub repository different-ai/agent-bank (255 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 491 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens