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.
git clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/commands/eddiebelaval/squire/visualize)<a href="https://agentmods.dev/commands/eddiebelaval/squire/visualize"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/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/commands/eddiebelaval/squire/visualize"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/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.00000 | $0.07317 |
| Opus 5 | $0.00000 | $0.03658 |
| Sonnet 5 | $0.00000 | $0.01463 |
| Haiku 4.5 | $0.00000 | $0.00732 |
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 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 — 678 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/visualize - Create Interactive Visual Explanation
Generate an interactive HTML visualization to explain a concept, system, architecture, codebase structure, or workflow visually. Eddie learns best through spatial, interactive visuals — not walls of text.
Instructions
When the user invokes /visualize [topic], create a single self-contained HTML file that visually explains the topic.
Step 1: Understand the topic
Determine what needs to be visualized. This could be:
- Architecture: System components, data flow, service boundaries
- Codebase map: File structure, module relationships, import chains
- Workflow: Step-by-step processes, decision trees, lifecycle stages
- Concept: Mental models, comparisons, trade-off matrices
- Status dashboard: Project health, task progress, deployment state
- Data flow: How data moves through the system, transformations, storage
If the topic is vague, explore the codebase first to gather real data before building the visualization.
Step 2: Design the visualization
Choose the right visual format:
- Tabbed views for multi-faceted topics (overview + details + cheatsheet)
- Flow diagrams for processes and pipelines
- Tree views for file structures and hierarchies
- Side-by-side comparisons for architecture layers or trade-offs
- Interactive cards that expand/collapse for progressive disclosure
- Color coding to group related concepts (consistent palette across views)
- Assessment tab (MANDATORY) — always include as the last tab. See "Senior Dev Assessment Tab" section below for full spec. This is what makes every artifact actionable.
Step 3: Build the HTML
Requirements:
- Single file, zero dependencies — no CDN links, no external CSS/JS
- Dark theme (Factory-inspired) — near-black background, warm neutrals, surgical accent color
- No emojis — use color and layout for visual hierarchy instead
- Interactive — clickable tabs, expandable sections, hover states
- Responsive — works on desktop and mobile (use CSS grid with breakpoints)
- Professional — generous whitespace, minimal borders, no shadows, no gradients
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 · 678 lines · 0 tokens per session scan A 3ccee2687ae4
visualize is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,317 tokens. 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-09-03.
Other commands, from other repositories
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
poc
Modo Prueba de Concepto para validar viabilidad técnica antes de comprometer implementación completa.
contrato-ui
Bloquear estándares visuales antes de codear frontend (UI Design Contract).
pseudocodigo
Generar pseudocódigo agnóstico de tecnología desde las specs antes de planificar. Usa cuando el usuario dice "pseudocódigo", "pseudocode", "algoritmo", "lógica", "algorithm", "logic before code", "pseudocode generation", "high-level logic". Convierte specs en pseudocódigo technology-agnostic antes de pasar a diseño…
ui-interactive
Interactive component wizard with step-by-step guidance and enforced quality gates.
icon-fetch
You are tasked with fetching icons from external design systems and integrating them into the Hogwarts unified icon system.