openwork: Skill for OpenCode

.opencode/skills/write-a-spec/SKILL.md

write-a-spec is a skill for OpenCode from different-ai/openwork. It costs 62 tokens per session (3,475 once invoked), scanned A, original, no licence file.

A workflow for writing automated end-to-end tests, which test a feature through its complete user flow, with the OpenWork testkit.

In plain words
What is it for?
Use it to write a test specification or create an end-to-end test in evals/specs.
Why use it?
It gives a defined place and format for turning a feature requirement into a repeatable test.

Skill for OpenCode

Written for OpenCode: installed under .opencode/.

This is different-ai/openwork's own configuration. It tells OpenCode how to work on openwork 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 openwork configures →

Reuse

Borrowing it

Nothing to install: this file belongs to different-ai/openwork. 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/openwork/dev/.opencode/skills/write-a-spec/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/different-ai/openwork

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 write-a-spec

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/different-ai/openwork/write-a-spec"><img src="https://agentmods.dev/badge/skills/different-ai/openwork/write-a-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,475 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin unknown 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.00062 $0.03475
Opus 5.5 $0.00025 $0.01390
Sonnet 5.5 $0.00012 $0.00695
Haiku 4.5 $0.00006 $0.00347

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

Security

Grade A, and why

write-a-spec 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 13d 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/skills/write-a-spec/SKILL.md · 262 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 13d ago Changed · +6 lines · +5 tokens per session f301c7a5e1c0
  2. 14d ago Changed · +10 lines b3aa1ef881a2
  3. 20d ago Changed 939159af2953
  4. 22d ago Changed · +8 lines a39ad2071c45
  5. 1mo ago Changed · +38 lines 86a64ab64db1
  6. 1mo ago Changed · +83 lines c046ec19fbe5
  7. 1mo ago Changed · +54 lines · +20 tokens per session 8f9a5f377c90
  8. 1mo ago Changed · +16 lines · -2 tokens per session 877f6eccd5a0
  9. 2mo ago First seen · 47 lines · 39 tokens per session scan A 1f522fab876d

Subscribe to this mod's changes

write-a-spec is a skill published in the GitHub repository different-ai/openwork (24,309 stars, last pushed today), with no licence file. It adds 62 tokens to every session and 3,475 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-30.

Related

Other skills, from other repositories

verify-omnigent

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…

omnigent-ai/omnigent · 100 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

eval-dataset-design

A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.

bojieli/ai-agent-book · 138 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

plugin87/ux-ui-agent-skills · 37 tokens