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/mi60dev/visionaire-engine/visionaire-verifynpx skills add mi60dev/visionaire-engine --skill visionaire-verifygit clone --depth 1 https://github.com/mi60dev/visionaire-engineWrote 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/mi60dev/visionaire-engine/visionaire-verify)<a href="https://agentmods.dev/skills/mi60dev/visionaire-engine/visionaire-verify"><img src="https://agentmods.dev/badge/skills/mi60dev/visionaire-engine/visionaire-verify.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.00079 | $0.00507 |
| Opus 5 | $0.00039 | $0.00253 |
| Sonnet 5 | $0.00016 | $0.00101 |
| Haiku 4.5 | $0.00008 | $0.00051 |
Grade A, and why
visionaire-verify 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
When this applies
Any turn where you edited a file that affects rendering (CSS/SCSS, styled-components, Tailwind classes, template/JSX markup, inline styles). If in doubt, verify.
The loop (do this every time, in order)
- BEFORE editing a shared selector (a class used in more than one place), call impact_preview { selector }. If it matches more than ~3 elements or spans multiple visual roles, tell the user what will be touched before you edit.
- Make the smallest edit that could fix the issue.
- AFTER the edit, verify — do NOT claim success from reading the code:
- If a suite exists for this area, call assert_visual { suite_id }.
- Otherwise state your claim as assertions, e.g. assert_visual { assertions: [{ type:"equal_height", targets:[{selector:".card"}] }] }.
- If the verdict is FAIL, read measured and offending_uids, then call diagnose { uid: , symptom:"auto" } and fix the named culprit. Repeat from step 2. Do not tell the user it is fixed until the verdict is PASS.
- For anything responsive, run responsive_sweep { run:{ suite_id } } across 375 / 768 / 1280 / 1920 before claiming done.
- When comparing to a mockup, use visual_diff { reference:{ image_path } } and drive divergence below the user's accepted threshold.
Hard rules
- Never say "now they are equal", "now it's centered", "this is fixed", or similar without a PASS verdict from assert_visual in the same turn.
- Report the actual measured numbers to the user (e.g. "412px vs 388px → now 400px vs 400px, PASS").
- If a tool returns TARGET_NOT_FOUND, your selector is wrong — re-check with find_elements, do not assume.
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 · 35 lines · 79 tokens per session scan A 2a5e3b221069
visionaire-verify is a skill published in the GitHub repository mi60dev/visionaire-engine (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 79 tokens to every session and 507 once invoked, about $0.0004 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
story-init
This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to begin a new fiction writing project from scratch.
character-management
This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character relationships", "character timeline", "character arc", "character profile", or needs to manage characters in a story project.
chapter-writing
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write prose for a story project.
plot-structure
This skill should be used when the user asks to "create a plot arc", "story structure", "add a plot point", "story timeline", "track foreshadowing", "pacing", "act structure", "story arc", "plot outline", or wants to plan and manage the narrative structure of a story.
worldbuilding
This skill should be used when the user asks to "create a location", "add a location", "magic system", "political system", "build the world", "add culture", "world history", "technology system", "religion", "economy", or wants to develop any aspect of a story's world and setting.
refactoring-ui
Apply UI design principles from Refactoring UI by Adam Wathan & Steve Schoger. Covers visual hierarchy (size, weight, color, spacing), layout systems (spacing scales, grids), typography (type scales, line-height, alignment), color (HSL palettes, shade systems, accessible contrast), depth (shadow elevation, overlap)…