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.
npx agentmods add commands/lookatitude/guild/plangit clone --depth 1 https://github.com/lookatitude/guildWhat 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 | $0.00044 | $0.02420 |
| Opus 5 | $0.00022 | $0.01210 |
| Sonnet 5 | $0.00009 | $0.00484 |
| Haiku 4.5 | $0.00004 | $0.00242 |
Grade A, and why
plan 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 2d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guild:plan — phase: Planning
The Planning phase entrypoint. Composes the team, writes the PRD and the
per-specialist lane plan, and authors the additive optional per-lane autonomy
contract. Team composition is a sub-step strictly inside this command
(its own approval gate); there is no standalone team command in v2 — inspect
via /guild:status, edit via the [edit] response at the plan/team approval
gate, raise the cap with --team-size=N.
Verb↔phase edge: /guild:plan → Planning. Phase concept binding:
lifecycle/phase-entrypoints.md · lifecycle/lifecycle-overview.md.
Contract binding
Before producer work begins, this phase resolves the frozen
guild.phase_entry.v1 contract. The additive optional per-lane
autonomy_contract is authored here and approved at the existing plan
gate — no new gate. The Tier-2 defaults: config folded at intake
is controlled by P1-config-001 — see /guild:config for the schema.
Usage
/guild:plan
/guild:plan --team-size=8
All five global flags + --dry-run apply. The --rigor profile expansion
(rigorProfile() in scripts/read-guild-config.ts) decides the L2 loop:
standard (the default) and deep both expand to a loops set containing
plan; only quick turns it off.
Args & local flags
- Args: — (no positional)
- Local flags:
--team-size=N— cap-6 override;>6prints a cap warning.
Gates (default)
- Team-approval I
- Plan/PRD-approval I
- G-planning review A
Output artifact
.guild/team/<slug>.<phase>.yaml + .guild/team/<slug>.current pointer,
the PRD (right-sized — inline ## PRD section in .guild/plan/<slug>.md
by default; promoted to a standalone .guild/prd/<slug>.md only when a
right-size trigger fires: >1 feature OR initiative-attached OR
success-criteria count >5 — ADR decisions/prd-right-sizing.md, folded
into the plan/PRD gate, no separate G-prd gate), .guild/plan/<slug>.md,
per-lane autonomy-contract policy (the additive autonomy_contract block
authored inside the plan), .guild/runs/<run-id>/review/plan/* (G-planning
broker trail).
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.
- 2d ago First seen · 202 lines · 44 tokens per session scan A f614bdfeb12d
plan is a command published in the GitHub repository lookatitude/guild (7 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 2,420 once invoked, about $0.0002 per session on Opus 5. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.