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/test-verify)<a href="https://agentmods.dev/commands/eddiebelaval/squire/test-verify"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/test-verify/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/test-verify"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/test-verify.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.01634 |
| Opus 5 | $0.00000 | $0.00817 |
| Sonnet 5 | $0.00000 | $0.00327 |
| Haiku 4.5 | $0.00000 | $0.00163 |
Grade A, and why
test-verify 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test and Verify
You are executing the test-verify workflow - runs tests and verifies the application works.
Pre-computed Context
# Detect project type
HAS_PACKAGE_JSON=$(test -f package.json && echo "yes" || echo "no")
HAS_PYPROJECT=$(test -f pyproject.toml && echo "yes" || echo "no")
HAS_SETUP_PY=$(test -f setup.py && echo "yes" || echo "no")
HAS_CARGO_TOML=$(test -f Cargo.toml && echo "yes" || echo "no")
HAS_GO_MOD=$(test -f go.mod && echo "yes" || echo "no")
HAS_MAKEFILE=$(test -f Makefile && echo "yes" || echo "no")
# Node.js detection
TEST_SCRIPT=$(cat package.json 2>/dev/null | jq -r '.scripts.test // "none"')
TYPECHECK_SCRIPT=$(cat package.json 2>/dev/null | jq -r '.scripts["type-check"] // .scripts.typecheck // "none"')
LINT_SCRIPT=$(cat package.json 2>/dev/null | jq -r '.scripts.lint // "none"')
BUILD_SCRIPT=$(cat package.json 2>/dev/null | jq -r '.scripts.build // "none"')
HAS_PLAYWRIGHT=$(test -f playwright.config.ts && echo "yes" || echo "no")
HAS_VITEST=$(grep -q "vitest" package.json 2>/dev/null && echo "yes" || echo "no")
HAS_JEST=$(grep -q "jest" package.json 2>/dev/null && echo "yes" || echo "no")
# Python detection
HAS_PYTEST=$(pip list 2>/dev/null | grep -q pytest && echo "yes" || echo "no")
HAS_MYPY=$(pip list 2>/dev/null | grep -q mypy && echo "yes" || echo "no")
HAS_RUFF=$(pip list 2>/dev/null | grep -q ruff && echo "yes" || echo "no")
# Shell detection
SHELL_SCRIPTS=$(find . -maxdepth 2 -name "*.sh" -type f 2>/dev/null | head -5)
HAS_SHELLCHECK=$(command -v shellcheck >/dev/null 2>&1 && echo "yes" || echo "no")
Project Type Detection:
- Node.js: $HAS_PACKAGE_JSON | Python: $HAS_PYPROJECT / $HAS_SETUP_PY | Rust: $HAS_CARGO_TOML | Go: $HAS_GO_MOD
Node.js: Test=$TEST_SCRIPT | TypeCheck=$TYPECHECK_SCRIPT | Lint=$LINT_SCRIPT | Build=$BUILD_SCRIPT | Playwright=$HAS_PLAYWRIGHT | Vitest=$HAS_VITEST | Jest=$HAS_JEST Python: Pytest=$HAS_PYTEST | Mypy=$HAS_MYPY | Ruff=$HAS_RUFF Shell: Scripts=$SHELL_SCRIPTS | Shellcheck=$HAS_SHELLCHECK
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 · 247 lines · 0 tokens per session scan A b9f1cb3f20d1
test-verify 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 1,634 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
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.
especificar
Crear especificaciones Gherkin desde un requerimiento/requisito. Usa cuando el usuario dice "escribir specs", "especificar feature", "crear Gherkin", "escribir requerimientos", "write specs", "requirements to Gherkin", "escribir scenarios", "documentar feature en Gherkin". Genera DBML schema auto-máticamente para…
implementar
Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.
spec-score
Puntuación cuantitativa de calidad de especificaciones (0-100) con 8 métricas. Usa cuando el usuario dice "spec score", "quality score", "spec quality", "completitud de specs", "IEEE 830", "ISO 29148", "spec assessment", "medir calidad specs". Score de 0-100 con 8 métricas: completitud, consistencia, verificabilidad…
tea
Testing Autónomo End-to-End (TEA): genera, ejecuta y reporta tests automáticamente. Usa cuando el usuario dice "E2E test", "test end-to-end", "correr tests", "generar tests", "testing suite", "run tests", "automated testing", "pruebas E2E", "test coverage", "regression testing". Detecta el framework de testing del…
visual-test
Testing visual de componentes UI y páginas con detección de regresiones visuales. Usa cuando el usuario dice "visual test", "snapshot test", "regression test UI", "visual regression", "UI test", "component test", "screenshot test", "Chromatic", "percy", "regred visual". Detecta cambios visuales en componentes y…