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 heyAyushh/stacc --skill visualizegit clone --depth 1 https://github.com/heyAyushh/staccWrote 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/heyayushh/stacc/visualize)<a href="https://agentmods.dev/skills/heyayushh/stacc/visualize"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/visualize/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/heyayushh/stacc/visualize"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/visualize.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.00045 | $0.00450 |
| Opus 5.5 | $0.00018 | $0.00180 |
| Sonnet 5.5 | $0.00009 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
visualize 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 1mo 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
Visualize - Generate Mermaid Diagram
Analyze input and generate clear, well-structured Mermaid diagrams.
Workflow
-
Analyze input - Understand what to visualize (code flow, architecture, data relationships, state machines, sequences, etc.)
-
Choose diagram type:
flowchart- Process flows, decision trees, algorithmssequenceDiagram- API calls, message passing, request/responseclassDiagram- Class structures, inheritance, interfaceserDiagram- Database schemas, entity relationshipsstateDiagram-v2- State machines, lifecycle flowsgraph TD/LR- Dependency graphs, module relationshipsgitgraph- Git branching strategiesjourney- User journeysgantt- Timelines and schedules
-
Generate diagram with:
- Clear, descriptive node labels
- Logical grouping with subgraphs where appropriate
- Consistent styling and direction
- Meaningful relationship labels on edges
- Manageable complexity (split if needed)
-
Output in mermaid code block:
```mermaid [diagram code] ```
Style Guidelines
- Use descriptive IDs:
userServicenota1 - Add labels to relationships when they add clarity
- Use subgraphs to group related components
- Keep readable: max ~15-20 nodes per diagram
- Arrow styles:
-->solid (main flow)-.->dotted (optional/async)==>thick (important path)o-->circle end (aggregation)*-->diamond end (composition)
After Generating
- Explain what the diagram shows
- Offer to refine or expand specific sections
- Suggest alternative diagram types if applicable
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.
- 1mo ago First seen · 57 lines · 45 tokens per session scan A 384c26110740
visualize is a skill published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 450 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
glance-canonical-layouts
Use this skill to create home screen widgets using Jetpack Glance Canonical Layouts from the Android Platform Samples project, or when asked to implement standard widget layout patterns (including Check List, Image Grid, Snap Scrolling, and Standard Toolbar).
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.