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/fix)<a href="https://agentmods.dev/commands/eddiebelaval/squire/fix"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/fix/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/fix"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/fix.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.00287 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
fix 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
/fix - Debug & Fix Issues
You are helping fix a bug or issue. Be thorough and systematic.
-
Understand the Problem
- Ask user to describe what's broken
- Ask what they expected to happen
- Ask what actually happens
- Get any error messages
-
Investigate
- Check browser console for errors (use Playwright MCP if needed)
- Review recent changes (git log)
- Identify likely files involved
- Check related tests
-
Diagnose
- Explain what's causing the issue in simple terms
- Use analogies: "The door won't open because..."
- Identify root cause, not just symptoms
-
Fix It
- Implement the fix
- Verify fix works with tests
- Check no new issues introduced
- Ensure accessibility/performance not impacted
-
Report Back
- Explain what was broken (simple terms)
- Explain what you fixed
- Confirm everything works now
- Suggest any preventive measures
-
Commit the Fix
- Format: "fix: [description of what was fixed]"
- Include reference to issue if applicable
Important:
- Use Playwright MCP to verify fixes visually
- Test edge cases
- Don't just patch symptoms - fix root cause
- Hooks will verify everything passes before completing
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 · 43 lines · 0 tokens per session scan A df0237195afd
fix is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 287 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
drift
Detectar divergencias entre specs Gherkin e implementación (spec drift). Usa cuando el usuario dice "spec drift", "drift detection", "spec vs código", "conformance check", "spec deviation", "código no matchea specs", "implementation diverged", "spec vs implementation", "verificar specs". Compara features implementadas…
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
diagnostico
Verificar la salud del setup de Don Cheli en el proyecto actual.
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
fire-test
Run Dominion Flow plugin integration tests to verify all commands and integrations work correctly.
verify-work
Validate built features through conversational UAT.