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 instructions/stardockcorp/wireloom/agents-mdgit clone --depth 1 https://github.com/StardockCorp/WireloomWrote 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/instructions/stardockcorp/wireloom/agents-md)<a href="https://agentmods.dev/instructions/stardockcorp/wireloom/agents-md"><img src="https://agentmods.dev/badge/instructions/stardockcorp/wireloom/agents-md.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.11434 | $0.11434 |
| Opus 5 | $0.05717 | $0.05717 |
| Sonnet 5 | $0.02287 | $0.02287 |
| Haiku 4.5 | $0.01143 | $0.01143 |
Grade A, and why
Wireloom AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 939 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wireloom for AI Agents
You are reading this because you need to render a UI wireframe mockup. Wireloom is a small text DSL for sketching user-interface layouts as inline SVG. This file is written for LLM agents (Claude, Codex, Cursor, etc.) that need to author wireframes — copy or link it into your agent's context when working on UI design tasks.
What is Wireloom?
Wireloom is a small indentation-based text language for UI wireframe mockups. You write a layout as indented plain text inside a ```wireloom fenced code block, and the Wireloom renderer turns it into an SVG wireframe. Output is monochrome, sketch-style — it reads as a mockup, not a finished UI.
Because Wireloom outputs plain SVG, the same block renders in GitHub, Obsidian, Notion, static site generators, or any Markdown tool that handles SVG. The read side needs no per-host plugin — only the authoring side needs the renderer (via npm install wireloom or a tool that bundles it).
When to Use Wireloom
Use Wireloom when the user asks for:
- "Mock up a screen / dialog / settings page / sign-in form…"
- "Draw a wireframe for…"
- "Sketch the layout of the new UI"
- "Show me how this feature would look"
- "Diagram the toolbar / inspector / split view"
- Any request about the shape of a user interface that isn't already a running app
When NOT to Use Wireloom
| If the user wants… | Use instead |
|---|---|
| Flowchart, sequence, class, ER, or state diagram | mermaid fenced block |
| Interactive prototype you can click through | A real component in their frontend framework (React, Svelte, Vue…) |
| Architecture / concept / dependency map with freeform nodes | A whiteboard/canvas tool or Mermaid graph |
| A real, working form or tool | Actual code in the target framework |
Wireloom is strictly for static structural mockups. If the ask is "can you make this tool / dashboard / page actually work?", write the real component instead.
Minimum Viable Wireframe
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 · 939 lines · 11,434 tokens per session scan A cb2a9f47c10b
Wireloom AGENTS.md is an instructions file published in the GitHub repository StardockCorp/Wireloom (52 stars, last pushed 1mo ago), licensed MIT. It adds 11,434 tokens to every session, about $0.0572 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-30.
Other instructions, from other repositories
solidworks-api-skill CLAUDE.md
Instructions for guoleizhen717/solidworks-api-skill, covering solidworks api skill repository, repository purpose, skill scope and project conventions.
q3ds-solidworks-mcp AGENTS.md
AGENTS.md instructions for zarcherlot/q3ds-solidworks-mcp, covering codex repository guidance, architecture, drawing planning and verification.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.