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/initiativegit clone --depth 1 https://github.com/lookatitude/guildWrote 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/lookatitude/guild/initiative)<a href="https://agentmods.dev/commands/lookatitude/guild/initiative"><img src="https://agentmods.dev/badge/commands/lookatitude/guild/initiative.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.01236 |
| Opus 5 | $0.00023 | $0.00618 |
| Sonnet 5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
initiative 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 today.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guild:initiative — durable-work noun (opt-in)
The opt-in durable-goal container. new|status|resume|update|close are the
primary user-facing lifecycle sub-verbs; list|archive|restore are
operational sub-verbs on the same noun.
Full lifecycle: docs/v2/initiatives.html (umbrella workspace canonical
design set — §Registry & directory, §Definition ledger, §The D8 close gate).
Sub-verb implementation: skills/meta/initiative/SKILL.md.
Sub-verbs
| Sub-verb | Drives | Gates | Output |
|---|---|---|---|
new |
create a durable goal container | definition-ready gate I | .guild/initiatives/active/<id>/initiative.yaml, definition-ledger |
status |
read initiative progress / work-items / release / doc-sync | R | prints state |
list |
list active initiatives (default) w/ cross-cut rollup; --archived shows all |
R | prints state |
resume |
re-enter at the next work-item | next gate I | continues initiative runs |
update |
amend the definition-ledger (--add-goal "…") |
ledger-change confirm I | updated ledger |
archive |
move to archived w/o close-gate release path (operational) | archive confirm I | active/<id>/ → archived |
restore |
restore archived → active (operational) | restore confirm I | archived → active/<id>/ |
close |
requires release evidence + doc-sync reconciliation (D8) | release-readiness + doc-sync gate I | active/<id>/release/** → archived |
Opt-in attachment binding
A one-off /guild:guild run does not create an initiative. An initiative is
attached only when (a) the user runs /guild:initiative … explicitly,
(b) --initiative=<id|new> is passed, or (c) the brief carries a
durable-goal signal — in which case /guild:guild asks "attach to an
initiative? [new / existing / one-off]" rather than auto-attaching. One-off
runs are first-class.
Run-start preflight (settings-control-and-tmux U3/U6)
Before the initiative skill is invoked — and before run-trace start — the run-trace CLI runs this preflight for you — you do not
call runStartPreflight yourself.
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.
- today Changed · +2 lines 1620643a3a8b
- 4d ago First seen · 85 lines · 47 tokens per session scan A 4f7b655a7d74
initiative is a command published in the GitHub repository lookatitude/guild (7 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 1,236 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
git
Git operations with intelligent commit messages and workflow optimization.
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.