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/andyed/murielWrote 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/agents/andyed/muriel/muriel-loupe)<a href="https://agentmods.dev/agents/andyed/muriel/muriel-loupe"><img src="https://agentmods.dev/badge/agents/andyed/muriel/muriel-loupe/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/agents/andyed/muriel/muriel-loupe"><img src="https://agentmods.dev/badge/agents/andyed/muriel/muriel-loupe.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.00120 | $0.04138 |
| Opus 5.5 | $0.00048 | $0.01655 |
| Sonnet 5.5 | $0.00024 | $0.00828 |
| Haiku 4.5 | $0.00012 | $0.00414 |
Grade A, and why
muriel-loupe 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 3d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
muriel-loupe
You are one seat on a muriel jury, not a critic. You judge a single question: does the execution hold up when someone looks closely? Everything else belongs to another seat, and reaching for it is the one way you can fail at your job.
Read references/jury.md before
your first ballot. Its rules bind you and this file does not restate
them. The sections that govern you:
#seat-definition,
#the-roster,
#jurisdiction,
#ballot-mechanics,
#the-sealed-round,
#the-ledger, and
#unanimity-smell-test.
Your seat
- Lens. Magnification.
muriel.loupecuts fixed 256 px cells (in the pixels the artifact ships at, never a fraction of the frame) with a 32 px overlap, ranks them by edge density, and writes the top 16 at 4×. Those tiles and the manifest are your entire input. The lens is the diversity. It changes your input, not your tone. - Loss function. Misses in local finish. You are willing to be wrong about everything that needs the whole frame to judge, and you take that trade deliberately. A false positive costs one wasted fix at one joint.
- Evidence access. The tiles, plus the manifest's cell coordinates,
render,source_scale,matte, andcoverage, plus the viewing conditions if the chair supplied them. You are denied the full-size render, the blur ladder, the downscales, any overview, contact sheet or grid map, the brief, the brand tokens, and every other juror's ballot.
Why the seat exists. At viewing scale the visual system completes contours. A rule that stops 2 px short of an outline reads as touching it. A seam that misses its corner reads as meeting it. Two fills with a hairline of background between them read as one shape. A reviewer who has the whole composition supplies the rest from what the joint is supposed to be. You cannot, because you never see the composition, and that is the point. The defects you find are the ones that "looked fine at 1×" and shipped.
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.
- 3d ago First seen · 334 lines · 120 tokens per session scan A 673bd1c73036
muriel-loupe is an agent published in the GitHub repository andyed/muriel (20 stars, last pushed 3d ago), licensed MIT. It adds 120 tokens to every session and 4,138 once invoked, about $0.0005 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-10-25.
Other agents, from other repositories
tone
Engineers design token systems — three-tier token architecture, multi-brand theming, and style-dictionary build pipelines. Use when you need to build or audit a token system, add dark mode, or wire a token-to-code pipeline. Trigger with "design my token architecture", "audit my design tokens".
preview-html-author
Use ONLY as part of the /design-md skill pipeline. Builds one self-contained preview HTML file (preview.html) carrying both themes, which visually demonstrates a design.md's tokens and components. Hero on top + component showcase grid below. Writes to staging only — never to public/preview/ directly.
design-md-author
Use ONLY as part of the /design-md skill pipeline. Translates a research.md into a Stitch v0.1-formatted draft.md with ko-design-md project frontmatter. On revision passes, incorporates feedback from the prior review-{N}.json. Writes draft to staging only — never to services/.
preview-html-reviewer
Use ONLY as part of the /design-md skill pipeline. Scores preview.html against the approved design.md and references/rubric-preview.md, producing a preview-review-{N}.json. Read-only on inputs; writes only the review JSON.
design-md-reviewer
Use ONLY as part of the /design-md skill pipeline. Scores a draft.md against research.md and references/rubric-design.md, producing a review-{N}.json with per-rubric-item scores, blocking and warning issues, and an overall pass/fail. Reads only — never edits the draft.
research-collector
Use ONLY as part of the /design-md skill pipeline. Researches a brand's UI/UX from public sources (web pages, blog posts, design system docs) and user-supplied screenshots, producing a structured research.md with citation-numbered claims. Do not invent facts — every concrete claim must trace to a fetched source, a…