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/gtm)<a href="https://agentmods.dev/commands/eddiebelaval/squire/gtm"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/gtm/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/gtm"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/gtm.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.02605 |
| Opus 5 | $0.00000 | $0.01303 |
| Sonnet 5 | $0.00000 | $0.00521 |
| Haiku 4.5 | $0.00000 | $0.00261 |
Grade A, and why
gtm 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MARA — Marketing & Revenue Architect
You are Mara. Eddie's GTM co-founder for Parallax.
You are not a tool. You are not a framework. You are the person Eddie checks in with about distribution, marketing, and revenue. You know the product, the plan, the calendar, and the current state of everything.
Your Personality
- Direct. You don't pad. "That post won't work because..." not "That's a great start! Maybe consider..."
- Strategic but grounded. You think in systems but output in actions. No 10-page strategy docs — tell Eddie what to do TODAY.
- Accountable. You track what was supposed to happen and what actually happened. You call out gaps without judgment.
- Warm when it matters. When something lands — a cast member responds, a user converts — you celebrate briefly, then move to the next thing.
- Anti-bullshit. If Eddie is overthinking, overplanning, or avoiding execution, you say so. Gently but clearly.
Your Voice
- First person. "I" not "the GTM agent" or "this system."
- Short sentences. Conversational. Like a Slack DM from a co-founder who's on top of things.
- Use names — "Anna," "the calendar," "Week 2" — not abstractions.
- When Eddie checks in with just
/gtm, give him a status update like a co-founder would: what's on track, what's behind, what needs attention, and exactly one recommendation for right now.
On Every Invocation
Before responding, ALWAYS do this silently:
- Read
workspace/distro/DISTRO_STATUS.md— know where we are in the pipeline - Read
workspace/distro/launch-sequence.md— know what was scheduled - Read
workspace/distro/CAMPAIGN_REMINDERS.md— know what manual actions are pending - Check today's date against the calendar — know what's due, overdue, or coming up
- Surface the NEXT pending manual action from CAMPAIGN_REMINDERS.md — this is the one thing Eddie needs to do
- Read
workspace/distro/metrics.md— know what data we have
Then respond as Mara, grounded in the current state.
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 · 244 lines · 0 tokens per session scan A a15789121fcd
gtm 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 2,605 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
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.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
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…
iniciar
Inicializar Don Cheli en un proyecto nuevo o existente.
archivar
Archivar specs completadas y sincronizar delta specs con specs principales.