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/luminary19/atelierWrote 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/luminary19/atelier/atelier-ship-reviewer)<a href="https://agentmods.dev/agents/luminary19/atelier/atelier-ship-reviewer"><img src="https://agentmods.dev/badge/agents/luminary19/atelier/atelier-ship-reviewer/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/luminary19/atelier/atelier-ship-reviewer"><img src="https://agentmods.dev/badge/agents/luminary19/atelier/atelier-ship-reviewer.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.00225 | $0.02305 |
| Opus 5 | $0.00112 | $0.01153 |
| Sonnet 5 | $0.00045 | $0.00461 |
| Haiku 4.5 | $0.00022 | $0.00231 |
Grade A, and why
atelier-ship-reviewer 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 10d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 10d ago First seen · 131 lines · 225 tokens per session scan A 28514cd7ac17
atelier-ship-reviewer is an agent published in the GitHub repository luminary19/atelier (2 stars, last pushed 2mo ago), with no licence file. It adds 225 tokens to every session and 2,305 once invoked, about $0.0011 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 agents, from other repositories
user-experience-designer
Adversarial UX and interaction designer who assumes the current interface is less than optimal. Audits features, screens, and flows for usability and interaction problems grounded in universal design, Nielsen's 10 heuristics, WCAG 2.2 accessibility, affordance and signifier clarity, microinteractions, goal-directed…
frontend-reviewer
Review React UI changes for behavior regressions, state consistency, and UX breakage.
frontend-code-reviewer
Frontend code review specialist. Invoke to review a frontend diff, pull request, or code snippet for React pattern correctness, TypeScript strictness, accessibility violations, performance regressions, CSS architecture, and test quality.
frontend-reviewer
Reviews frontend code for design system compliance, accessibility, and responsive patterns. Use after frontend code changes.
qa-verifier
Use to independently verify a running frontend - drive key flows, assert ZERO browser console errors, run accessibility (WCAG AA) and Lighthouse checks, and confirm the UI matches DESIGN.md - then return a pass/fail report with evidence. Invoke before claiming a phase or the project "done".
react-frontend
React Frontend Execution Agent.