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 skills add tjboudreaux/cc-plugin-text-visualizations --skill tools-visual-state-machinesgit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-text-visualizationsWrote 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/tjboudreaux/cc-plugin-text-visualizations/tools-visual-state-machines)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-state-machines"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-state-machines/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.
<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-state-machines"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-state-machines.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.00337 |
| Opus 5 | $0.00013 | $0.00169 |
| Sonnet 5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
tools-visual-state-machines 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 9d 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.
What it actually says
State Machine Storyboards
Intent
- Explain how users or issues move through states with clear entry/exit rules.
- Support growth loop, launch, or issue triage skills by making transitions explicit.
Inputs
- State list (e.g.,
New,Activated,Retained,Churned). - Transition triggers (events, metrics, timers).
- Guard conditions / actions per transition.
Workflow
- Define legend
[STATE]boxes; arrows-->; dotted..>for optional transitions.
- Draft storyboard
- Example:
[New] | | signup complete v [Activated] --fails SLA--> [Churn Risk] | retention event v [Retained]
- Example:
- Add annotations
- Edge labels:
>=3 sessions,NPS<30. - Actions:
/{ send email }appended to arrow.
- Edge labels:
- Link to metrics
- Provide query references or analytics dashboards for each transition.
- Embed in docs
- Include in PRs/issues or
.factory/skills/...referencing file names (e.g.,state-machines/activation.txt).
- Include in PRs/issues or
Verification
- Every state has at least one ingress and egress (unless Start/End).
- Triggers clearly defined; no unlabeled arrows.
- Diagram reviewed with product/growth stakeholders for accuracy.
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.
- 9d ago First seen · 44 lines · 25 tokens per session scan A 361e0855db7e
tools-visual-state-machines is a skill published in the GitHub repository tjboudreaux/cc-plugin-text-visualizations (2 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 337 once invoked, about $0.0001 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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…