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/buildgit 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.00051 | $0.02746 |
| Opus 5 | $0.00026 | $0.01373 |
| Sonnet 5 | $0.00010 | $0.00549 |
| Haiku 4.5 | $0.00005 | $0.00275 |
Grade A, and why
build 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guild:build — phase: Development
The Development phase entrypoint. Assembles per-specialist context and
dispatches lanes. The backend (agent_mode) is resolved once at command
intake via the run-start preflight snapshot — it is not selected per-phase.
snapshot.effective.agent_mode (team / agent / subagent) drives lane
dispatch; execute-plan reads it from the locked-in snapshot rather than
re-resolving. An optional positional [lane-id] re-runs a single lane.
Verb↔phase edge: /guild:build → Development. 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 run executes under the
task_run.autonomy_policy recorded in the approved plan (the autonomy
contract was set at plan approval; no new gate).
Usage
/guild:build
/guild:build lane-backend-001
All five global flags + --dry-run apply.
Args & local flags
- Args:
[lane-id](re-run one lane) - Local flags:
--model-tier=cheap|mid|powerful— top-precedence tiering override; forces every lane in this run to the given model tier regardless of per-lane plan overrides or themodels:settings block. Precedence:--model-tier> per-lanemodel_tier:>settings.json models:> built-in. Ref:docs/v2/config-surfaces.html §5. DRIFT-ANALYSIS CMD-008.
Gates (default)
- Autonomy contract (set at plan approval) A
- G-lane review A (per lane, via
guild:review-broker; policy-gated — fires whenrisk ≥ highOR--review=crossOR project config requires it) - Destructive / network ops I always (immutable always-ask hard set —
never relaxed by
--auto-approve)
Output artifact
.guild/context/<run-id>/<specialist>-<task-id>.md (per-lane context
bundles), .guild/runs/<run-id>/handoffs/*.md (guild.handoff_receipt.v1),
.guild/runs/<run-id>/assumptions.md, .guild/runs/<run-id>/review.md,
.guild/runs/<run-id>/review/G-lane:<task-id>/ (G-lane broker trail per lane),
.guild/runs/<run-id>/agent-bus/events.ndjson,
.guild/runs/<run-id>/verify.md (guild:verify-done), changed files.
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 · 217 lines · 51 tokens per session scan A ce034aa6d68c
build is a command published in the GitHub repository lookatitude/guild (7 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 2,746 once invoked, about $0.0003 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
add-portal
You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic linkedin-search and freehire-search), and the README invites users elsewhere to build equivalents — this command turns that invitation…
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
execute
Delegate execution to GJC (runs /skill:ultragoal to completion with verification).
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.