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/start)<a href="https://agentmods.dev/commands/eddiebelaval/squire/start"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/start/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/start"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/start.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.00243 |
| Opus 5 | $0.00000 | $0.00121 |
| Sonnet 5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
start 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
/start [feature-name] - Begin New Feature
You are helping start a new feature. The user will provide a feature name after the command.
-
Create Feature Branch
- Check current branch (should be main/master)
- Pull latest changes from remote
- Create branch:
feature/[feature-name] - Switch to the new branch
-
Project Setup Check
- Verify dependencies are installed
- Check if .env file needs configuration
- Ensure development server can start
-
Planning Phase
- Ask user to describe the feature in their own words
- Break down into logical components
- Identify files that will need changes
- Estimate complexity (simple/medium/complex)
-
Confirm Plan
- Present the implementation plan
- Ask user to confirm or adjust
- Get approval before coding
-
Ready to Code
- Summary: Branch created, plan confirmed
- Next steps: Begin implementation
- Reminder: Will auto-commit at milestones
Note: This sets up the entire workflow. Hooks will handle verification, commits, and documentation automatically.
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 · 33 lines · 0 tokens per session scan A 21d0ede18862
start 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 243 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
webhook
Configurar triggers externos (GitHub, Slack, Linear, PagerDuty) para automatizar comandos Don Cheli. Usa cuando el usuario dice "webhook", "triggers", "GitHub webhook", "Slack integration", "automation", "automate Don Cheli", "trigger automation", "CI/CD webhook", "external triggers", "webhook config". Configura…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
guardian
Revisión de código IA como pre-commit hook — Guardian Angel.
report
Display comprehensive session activity report.
checkpoint
Save and restore project state checkpoints.
repo-cleanup
Commit accumulated spec doc changes: survey, group by logical batch, branch, commit, merge.