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/preview)<a href="https://agentmods.dev/commands/eddiebelaval/squire/preview"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/preview/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/preview"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/preview.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.00404 |
| Opus 5 | $0.00000 | $0.00202 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
preview 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.
What it actually says
/preview - Preview Changes Before Committing
You are helping review changes before they're committed. Be thorough.
-
Show What Changed
- List all modified files
- Categorize by type (UI, logic, config, etc.)
- Highlight new vs modified vs deleted
-
For Each Changed File
File: [name]
- 📝 What changed: [Plain English summary]
- 🎯 Why: [Purpose of change]
- ⚠️ Impact: [What this affects]
- ✅ Tests: [Passing/needs tests]
-
Quality Checks Run automatic checks:
- ✅ TypeScript types valid
- ✅ Linting passes
- ✅ Tests passing
- ✅ Build succeeds
- ✅ No console errors
- ✅ Accessibility maintained
-
Visual Preview (if UI changes)
- Use Playwright to screenshot changes
- Show before/after (if possible)
- Check responsive design
- Test interactions
-
Risk Assessment
🔴 High Risk Changes:
- [List any risky changes]
🟡 Medium Risk:
- [List moderate changes]
🟢 Low Risk:
- [List safe changes]
-
Commit Recommendation
Ready to Commit? [Yes/No]
If Yes:
- ✅ All checks pass
- ✅ Changes tested
- ✅ Documentation updated
- Suggested commit message: "[message]"
If No:
- ⚠️ Issues to fix: [List]
- 🔧 Will fix before committing
-
Next Steps
- Commit now?
- More changes needed?
- Ready for PR?
Remember:
- Use Playwright to actually see UI changes
- Don't guess - verify everything
- Be honest about risks
- Suggest fixes for any issues found
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 · 68 lines · 0 tokens per session scan A 2d8127e3abcc
preview 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 404 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
audio-pass
Functional audio review for implementation, mix coverage, clarity, and player feedback.
ipd-tr
A command that runs a staged technical review process involving quality, testing, architecture, and requirements checks before a release decision. IPD-OMO is the process named in the add-on; its specialized role names are not explained further in the input.
wize-tea-review
Goal. A structured review of one story before its gate decision. Distinct from Shuri's wize-code-review (which audits code health). This one audits AC fulfillment, test discipline, and risk-spot coverage.
code-review
Comprehensive 3-pass code review of uncommitted changes. Covers quality (security, React, Node.js, performance), compliance (CLAUDE.md rules), and contract consistency (cross-repo API types).
verify-work
Validate built features through conversational UAT.
gx-e2e-review
You will be supplied with a commit or a directory or a test file. Your job is to review the E2E (Selenium/Playwright) tests.