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/tjboudreaux/cc-plugin-text-visualizations/tools-visual-workflowsnpx skills add tjboudreaux/cc-plugin-text-visualizations --skill tools-visual-workflowsgit 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-workflows)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-workflows"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-text-visualizations/tools-visual-workflows.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.00031 | $0.00391 |
| Opus 5 | $0.00015 | $0.00196 |
| Sonnet 5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
tools-visual-workflows 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 4d 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
Visual Workflow Blueprints
Intent
- Speed up comprehension of complex processes (PR lifecycle, launch plan, triage ops) via monospaced diagrams.
- Provide reusable templates and conventions for both macOS/Linux terminals and Windows consoles.
Inputs
- Workflow steps, roles, decision points.
- Target medium (GitHub comment, Slack, Notion, terminal output).
- Required metadata (owners, SLAs, tools).
Workflow
- Select diagram type
- Flowchart (boxes/arrows) for branching logic.
- Timeline/swimlane for sequential steps.
- Use standard glyphs
- Start/End:
(start)(end) - Process:
[ action ] - Decision:
{ condition? } - Arrows:
-->,==>,~~>for async.
- Start/End:
- Build with templates
- Flow template:
(start) | [Step 1] | {Decision?} / \
Day 0 Day 3 Day 7 |-----|-----|-----| Dev QA Launch- Timeline template: - Flow template:
- Annotate with data
- Include owners (
@alice), tooling (gh pr checks), or SLA markers (<24h).
- Include owners (
- Validate readability
- View in plain text viewer; avoid tabs; max width 80 chars.
Verification
- Diagram renders without wrapping in GitHub/CLI.
- Each decision path labeled clearly.
- Stored alongside workflow documentation (e.g.,
.factory/docs/visuals).
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.
- 4d ago First seen · 52 lines · 31 tokens per session scan A 04b15dd32f4e
tools-visual-workflows is a skill published in the GitHub repository tjboudreaux/cc-plugin-text-visualizations (2 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 391 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
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…