A workflow for OpenSpec, a command-line system that records proposed software changes as reviewable specifications and task lists. It covers exploring an idea, proposing and applying changes, syncing specifications, and archiving completed work.

Use it to investigate a change, write its proposal and design, implement listed tasks, update the main specifications, and finish the change record.

It keeps the reasoning, design, requirements, and implementation tasks for a change organized across sessions.

How Jonnyton/TinyAssets configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to Jonnyton/TinyAssets. 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/Jonnyton/TinyAssets/main/.agents/skills/openspec/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Jonnyton/TinyAssets

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jonnyton/tinyassets/openspec/github.svg)](https://agentmods.dev/skills/jonnyton/tinyassets/openspec)

Your own site

<a href="https://agentmods.dev/skills/jonnyton/tinyassets/openspec"><img src="https://agentmods.dev/badge/skills/jonnyton/tinyassets/openspec/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jonnyton/tinyassets/openspec"><img src="https://agentmods.dev/badge/skills/jonnyton/tinyassets/openspec.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 1,382 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.

Model	Per session	Once invoked
Fable 5.1	$0.00062	$0.01382
Opus 5.5	$0.00025	$0.00553
Sonnet 5.5	$0.00012	$0.00276
Haiku 4.5	$0.00006	$0.00138

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

Security

Grade A, and why

openspec 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 2mo 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.

.agents/skills/openspec/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenSpec

Requires the openspec CLI (MIT, Fission-AI/OpenSpec; npm i -g @fission-ai/openspec). Specs live in the repo and persist across sessions. This is the CLI-managed, multi-session spec system. Where the CLI is unavailable, hand-write a change directory matching the OpenSpec layout (proposal.md, design.md, delta specs, tasks.md) so it can be adopted once the CLI is back — see AGENTS.md § Spec-driven development.

Lifecycle

explore → propose → apply → sync-specs → archive
(think)   (artifacts) (build) (merge deltas) (finalize)

Each is an action on a change, not a rigid phase — invoke any of them anytime. Always orient first with openspec list --json (active changes) and openspec status --change "<name>" --json (schema, paths via planningHome / changeRoot / artifactPaths / actionContext). Use those resolved paths — never assume repo-local paths. If status reports actionContext.mode: "workspace-planning" with empty allowedEditRoots, that operation isn't supported in this slice — treat linked repos/folders as read-only and STOP before editing.

At dispatch/triage time, also run python scripts/openspec_flow.py audit and finish existing delivery WIP before admitting more. This is on-demand flow control, not a mandatory session-start step.

explore — a thinking partner

A stance, not a workflow: curious, visual (ASCII diagrams liberally), adaptive, grounded in the actual codebase. Never write code or implement features in explore mode — you may read/search/investigate and create OpenSpec artifacts (that's capturing thinking), but if asked to implement, tell the user to exit explore and create a proposal. Offer to capture crystallized insights into the right artifact (requirement → specs, design decision → design.md, scope → proposal.md, new work → tasks.md); the user decides — don't auto-capture.

propose — generate all artifacts

Create a change and its artifacts in one pass. Derive a kebab-case name from the user's description (don't proceed without understanding what they want): openspec new change "<name>" → openspec status --change "<name>" --json for the build order (applyRequires, artifacts with dependencies). Loop through ready artifacts in dependency order: openspec instructions <artifact-id> --change "<name>" --json gives template (structure to write), resolvedOutputPath, and context/rules (constraints for YOU — never copy these blocks into the file). Read completed dependencies for context, write each artifact, re-check status, until every applyRequires artifact is done. Verify each file exists before moving on.

Read the full file on GitHub · 106 lines

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.

2mo ago First seen · 106 lines · 62 tokens per session scan A 50e2e2a08725

Subscribe to this mod's changes

openspec is a skill published in the GitHub repository Jonnyton/TinyAssets (1 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,382 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.

Planning

openspec next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
openspecJonnyton/TinyAssets	Skill	1	1mo ago	MIT	A	62	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

TinyAssets: Skill for Claude Code