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 agentmods add skills/synaptiai/agent-capability-standard/transitionnpx skills add synaptiai/agent-capability-standard --skill transitiongit clone --depth 1 https://github.com/synaptiai/agent-capability-standardWrote 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/synaptiai/agent-capability-standard/transition)<a href="https://agentmods.dev/skills/synaptiai/agent-capability-standard/transition"><img src="https://agentmods.dev/badge/skills/synaptiai/agent-capability-standard/transition.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.02022 |
| Opus 5 | $0.00017 | $0.01011 |
| Sonnet 5 | $0.00007 | $0.00404 |
| Haiku 4.5 | $0.00003 | $0.00202 |
Grade A, and why
transition 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 5d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent
Define the rules governing how a system's state changes over time. This capability captures state machine semantics: what triggers transitions, what preconditions must hold, and what effects occur.
Success criteria:
- Transition rules clearly specified
- Preconditions and effects documented
- Triggers identified with evidence
- State machine is deterministic (or non-determinism noted)
Compatible schemas:
schemas/output_schema.yaml
Inputs
| Parameter | Required | Type | Description |
|---|---|---|---|
from_state |
Yes | object | Initial state or state pattern |
to_state |
No | object | Target state (optional for discovery mode) |
triggers |
No | array | Events or conditions that cause transition |
scope |
No | string | Domain to analyze for transitions |
Procedure
-
Identify state variables: Determine what can change
- Extract mutable properties from state model
- Identify discrete vs continuous variables
- Note invariants (what cannot change)
-
Discover triggers: Find what causes state changes
- Identify events (user actions, system events)
- Find conditions (thresholds, timeouts)
- Note external inputs that affect state
-
Define preconditions: Specify when transitions can occur
- Document required state for transition
- Identify guards and conditions
- Note blocking conditions
-
Specify effects: Document what changes during transition
- List state variable changes
- Note side effects (events emitted, actions taken)
- Capture ordering constraints
-
Validate completeness: Check for missing transitions
- Identify unreachable states
- Find states with no outgoing transitions
- Note non-deterministic cases
-
Ground rules: Document evidence for each transition rule
- Reference code, configuration, or documentation
- Note confidence in each rule
Output Contract
Return a structured object:
rules:
- id: string # Unique rule identifier
name: string # Human-readable name
from: object # Source state pattern
to: object # Target state pattern
trigger:
type: string # event, condition, timeout
specification: any # Trigger details
preconditions: array[string] # Required conditions
effects: array[string] # State changes
priority: number # Resolution priority for conflicts
analysis:
reachability: object # Which states are reachable
completeness: number # Coverage estimate
non_determinism: array # Ambiguous transitions
confidence: 0..1
evidence_anchors: ["file:line", "doc:section"]
assumptions: []
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 293 lines · 34 tokens per session scan A b5e5ad14bc68
transition is a skill published in the GitHub repository synaptiai/agent-capability-standard (4 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,022 once invoked, about $0.0002 per session on Opus 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
gh
GitHub API access and project management automation for the hallucination-detector repo. Uses octokit with proxy-aware client for all GitHub operations — issues, PRs, labels, milestones, Projects V2. No gh CLI required.
evaluate-options
Research and evaluate implementation options before presenting a recommendation. Use when multiple approaches exist for a problem and a decision is needed. Launches one background research agent per option in parallel, collects evidence-backed findings, then presents a recommendation grounded in observed data — not…
delegate
Quick delegation template for sub-agent prompts. Use when assigning work to a sub-agent, before invoking the Task tool, or when preparing prompts for specialized agents. Provides the WHERE-WHAT-WHY framework. For comprehensive delegation guidance, activate the agent-orchestration how-to-delegate skill.
beginner-tone
코딩도 AI도 처음인 초보자와 대화할 때 쓰는 말투·안전 지침. SoDamHarness 설치 시 자동 활성화.
sodam-harness-self-check
작업을 끝내거나 "다 됐어요"라고 말하기 전에 실제로 작동하는지 점검하고 증거를 보여줄 때 사용. 위험·중요 작업 마무리, 완료 선언, 검증 요청 시 적용.
ai-safe-driver
Use when the agent keeps repeating a mistake, ignores a correction, retries a failed tool unchanged, breaks an output format again, drifts from the latest request, or makes excuses instead of diagnosing recurrence. Also use for a conversation health check, compaction decision, or new-session question.