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/compare)<a href="https://agentmods.dev/commands/eddiebelaval/squire/compare"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/compare/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/compare"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/compare.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.00332 |
| Opus 5.5 | $0.00000 | $0.00133 |
| Sonnet 5.5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
compare 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 1mo 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
/compare - Compare Changes
You are helping visualize what changed. Make it clear and actionable.
-
Determine Comparison Ask what to compare:
- Current changes vs last commit
- Current branch vs main
- Two specific commits
- Before/after a specific file
-
Show Summary Stats
📊 Changes Summary: - Files changed: [count] - Lines added: [count] - Lines removed: [count] - Net change: [+/- count] -
Categorize Changes Group by type:
🎨 UI/Frontend
- [List files]
⚙️ Logic/Backend
- [List files]
🗄️ Database
- [List files]
📝 Documentation
- [List files]
✅ Tests
- [List files]
-
Highlight Key Changes For each important file:
- What changed in plain English
- Why it matters
- Any potential issues
-
Visual Diff (if requested)
- Show specific file changes
- Explain what the changes do
- Use simple language
-
Impact Assessment
- Breaking changes? (yes/no)
- Affects existing features? (list)
- New dependencies? (list)
- Performance impact? (better/worse/neutral)
Output Style:
- Visual and organized
- Plain English explanations
- Focus on WHAT changed and WHY it matters
- Flag any concerns or risks
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.
- 1mo ago First seen · 61 lines · 0 tokens per session scan A 18007612fdc2
compare is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 332 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-08-30.
Other commands, from other repositories
review-pr
Review a pull request (GitHub) or merge request (GitLab) and provide detailed feedback.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
create-pr
Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation. Runs parallel checks (tests, lint, type-check, security) before opening. Supports feature, bugfix, refactor, and hotfix PR types with milestone assignment via gh CLI. Invoke only if the operator…
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
implement-issue
Implement a GitHub issue or GitLab issue and create a PR/MR.
auto-review.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure Example output.