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/deploy)<a href="https://agentmods.dev/commands/eddiebelaval/squire/deploy"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/deploy/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/deploy"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/deploy.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.00845 |
| Opus 5.5 | $0.00000 | $0.00338 |
| Sonnet 5.5 | $0.00000 | $0.00169 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
deploy 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy - Production Deployment
Detect project, verify readiness, trigger deploy, and confirm live.
Pre-computed Context
PROJECT_NAME=$(basename $(pwd))
HAS_VERCEL=$(test -f .vercel/project.json && echo "yes" || echo "no")
VERCEL_PROJECT=$(cat .vercel/project.json 2>/dev/null | jq -r '.projectId // "unknown"')
CURRENT_BRANCH=$(git branch --show-current)
OPEN_PRS=$(gh pr list --state open --json number,title,headRefName 2>/dev/null)
LAST_DEPLOY=$(vercel ls --limit 1 2>/dev/null | tail -1)
Project: $PROJECT_NAME Vercel Configured: $HAS_VERCEL Current Branch: $CURRENT_BRANCH Open PRs: $OPEN_PRS
Usage
/deploy # Deploy current project to production
/deploy --status # Check current deployment status
/deploy --rollback # Revert to previous deployment
/deploy --preview # Deploy preview (non-production)
User Intent
$ARGUMENTS
Deploy Workflow
Step 1: Pre-flight Checks
- Verify on main branch (or confirm intent to deploy from feature branch)
- Check for unmerged PRs that should go out first
- Run quick verification:
npm run build && npx tsc --noEmit
- Check git status — warn if uncommitted changes exist
Step 2: Trigger Deployment
Auto-deploy from main (default):
git push origin main
# Vercel auto-deploys from main
Manual production deploy:
vercel --prod
Step 3: Monitor Deploy
Use /deploy-watch for monitoring. Two options:
Option A (interactive): /loop 30s /deploy-watch — polls every 30s, you see updates in real time
Option B (background): Set up a CronCreate job with /deploy-watch every 2 min — monitors while you work on other things
If neither is requested, fall back to inline polling (every 10s, timeout at 5 min):
- Report deployment URL
- Check HTTP status of production URL
Step 4: Smoke Test
- Hit the root URL — verify 200 response
- If API routes exist, hit
/api/healthor equivalent - Use Playwright MCP to take a screenshot of the live site
- Report pass/fail
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 · 121 lines · 0 tokens per session scan A c2a681f4e78f
deploy 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 845 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
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:help
Show available PAUL commands and usage guide.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
architect
Generate architecture.md with system design decisions from foundation documents.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.