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/typefox/agent-skills/statemachine-dslnpx skills add TypeFox/agent-skills --skill statemachine-dslgit clone --depth 1 https://github.com/TypeFox/agent-skillsWrote 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/typefox/agent-skills/statemachine-dsl)<a href="https://agentmods.dev/skills/typefox/agent-skills/statemachine-dsl"><img src="https://agentmods.dev/badge/skills/typefox/agent-skills/statemachine-dsl.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.00063 | $0.00911 |
| Opus 5 | $0.00032 | $0.00456 |
| Sonnet 5 | $0.00013 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
statemachine-dsl 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statemachine DSL
A small textual language for describing finite state machines: a named machine, the events it recognizes, optional commands, an initial state, and a set of states connected by transitions.
File structure
A file is one machine, in this fixed order:
statemachine <Name>
events
<eventName>
<eventName>
commands
<commandName>
initialState <StateName>
state <StateName>
actions { <commandName> }
<eventName> => <TargetStateName>
end
statemachine <Name>— required header naming the machine.<Name>is an identifier ([_a-zA-Z][\w_]*).events— optional block listing one or more event names, one per line (whitespace separated).commands— optional block listing one or more command names.initialState <StateName>— required; must reference a state defined in the file.state ... end— zero or more state definitions.
Syntax (EBNF)
statemachine_file = "statemachine", identifier,
[ events_block ], [ commands_block ],
"initialState", state_ref,
{ state } ;
events_block = "events", { event_name } ;
commands_block = "commands", { command_name } ;
state = "state", identifier,
[ actions_clause ],
{ transition },
"end" ;
actions_clause = "actions", "{", { command_ref }, "}" ;
transition = event_ref, "=>", state_ref ;
event_name = identifier ;
command_name = identifier ;
event_ref = identifier ; (* must match a declared event *)
command_ref = identifier ; (* must match a declared command *)
state_ref = identifier ; (* must match a defined state *)
identifier = letter, { letter | digit | "_" } ;
letter = "A" | "B" | ... | "Z" | "a" | "b" | ... | "z" ;
There is no closing end for the whole machine — only each state block ends with end.
States and transitions
Each state is a state <Name> ... end block containing:
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 · 127 lines · 63 tokens per session scan A 828f3aea87f2
statemachine-dsl is a skill published in the GitHub repository TypeFox/agent-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 63 tokens to every session and 911 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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.
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…