A way to define requirements and success criteria for changes to SysMLv2 models. Success criteria describe how you will know the model enhancement is complete and correct.

Use it to write the expected behavior, constraints, and completion checks for a SysMLv2 model enhancement.

It gives modeling work a clear target before implementation begins and makes later checking more objective.

How 1cFE/fusion-tea configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to 1cFE/fusion-tea. 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/1cFE/fusion-tea/main/.agents/skills/spec-model/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/1cFE/fusion-tea

Made for: Claude Code.

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/1cfe/fusion-tea/spec-model/github.svg)](https://agentmods.dev/skills/1cfe/fusion-tea/spec-model)

Your own site

<a href="https://agentmods.dev/skills/1cfe/fusion-tea/spec-model"><img src="https://agentmods.dev/badge/skills/1cfe/fusion-tea/spec-model/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/1cfe/fusion-tea/spec-model"><img src="https://agentmods.dev/badge/skills/1cfe/fusion-tea/spec-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 725 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.00016	$0.00725
Opus 5.5	$0.00006	$0.00290
Sonnet 5.5	$0.00003	$0.00145
Haiku 4.5	$0.00002	$0.00072

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

Security

Grade A, and why

spec-model 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 24d 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/spec-model/SKILL.md · 54 lines

How it starts

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

Before executing this skill, read .agentic-mbse/claude.md in Claude Code or .agentic-mbse/codex.md in Codex. Resolve supporting paths from this skill’s installed directory; keep generated outputs in the project or a temporary directory. Read referenced skills from .agents/skills/<name>/SKILL.md when their guidance is needed.

Spec Model

Use “Process Selection” in modeling_project/MODELING_PROCESS.md. This stage may be brief or skipped when its responsibility is already satisfied. For a bounded tracked change, use sections in the existing spec.md instead of creating separate design/plan documents; retain required native metadata. The instructions below describe a separate artifact when it is useful.

Define the intended modeling outcome, requirements, and supported use. Write work/active/{WI-XXX}_{name}/spec.md using the project's native work-item registration and metadata conventions.

Understand the Need

Inspect knowledge/SOURCE_INDEX.md and knowledge/KNOWLEDGE.md for relevant current authority and insights, unless already loaded and current. Read the request, relevant epic outcomes, project requirements, and existing research/models. Follow their source references selectively. Identify what someone needs to understand, change, compare, or decide using the model, and what currently prevents that.

Ask only questions whose answers materially change scope, meaning, or success. Use existing authorization; under orchestration, route questions to the coordinator. Leave implementation choices to design unless an owner decision or an existing interface requires them.

Capture the Contract

Keep the spec proportional to the work:

Problem and intended use, including the structural or behavioral understanding needed alongside numerical results.
Requirements and success criteria with source provenance, meaningful expected behavior, and applicable preservation obligations. Where the design-choice row of the technical-pattern table in modeling_project/MODELING_PROCESS.md applies, name the design choices the consumer must keep (design-choices.md).
Scope and supported-domain limits, affected consumers, assumptions, and unresolved questions.
References to the epic, research, and governing project decisions.

Read the full file on GitHub · 54 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.

24d ago Changed · -7 lines 53522328e042
1mo ago First seen · 61 lines · 16 tokens per session scan A dbf43bad1114

Subscribe to this mod's changes

spec-model is a skill published in the GitHub repository 1cFE/fusion-tea (5 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 725 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-09-29.

Planning

spec-model next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spec-model1cFE/fusion-tea	Skill	5	24d ago	MIT	A	16	Claude Code
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	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

fusion-tea: Skill for Claude Code