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/auditgit 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.00043 | $0.00688 |
| Opus 5 | $0.00022 | $0.00344 |
| Sonnet 5 | $0.00009 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
audit 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guild:audit — self-maintenance (Guild-on-Guild)
Static security audit of installed Guild scripts. Maps to skill
guild:audit. R static analysis — includes the static
boundary-check section.
Gates
None — R (static analysis only).
Output
.guild/audit/<date>.md, including the boundary-check section: it scans
for any Guild-owned-file signature (frontmatter type:, a
schema_version: guild.* marker, or a task_run-declared artifact kind)
written outside the consuming repo's .guild/ (including any runtime
write into the plugin install dir) and flags each as a boundary violation.
This is the static belt to the PreToolUse guard's runtime suspenders; both
reuse existing surfaces and add no new gate.
Run-start preflight (settings-control-and-tmux U3/U6)
Before the static audit begins — and before run-trace start — the run-trace CLI runs this preflight for you — you do not
call runStartPreflight yourself.
Since wave 2, run-trace.js start (below) is the sole caller of
runStartPreflight (scripts/lib/runstart-preflight.ts; canonical contract in
guild.md §Run-start preflight): on start the CLI resolves the 7-source
inheritance chain, validates closed keys, probes tmux, detects providers, and
writes .guild/runs/<id>/resolved-settings.json (+ a compact settings_ref in
run.yaml) automatically before the run opens. If this command needs the
resolved config — e.g. the dispatch backend effective.agent_mode — read the
snapshot back with readResolvedSettingsSnapshot(runId, { cwd }); never
re-resolve.
Run recording
Before the audit skill is invoked, start a run (SC-B, §435):
node ${GUILD_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-$HOME/.local/share/guild/dist/claude-code}}/hooks/dist/run-trace.js start \
--command=/guild:audit \
--cwd "$(pwd)"
run-class default (full). Records the run before the SHA-256 hash scan
so the complete session — boundary-check and static analysis — is replayable
from the entrypoint. Audit writes to .guild/audit/ — not
.guild/initiatives/ (NN#5 unaffected). No --initiative flag.
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 · 70 lines · 43 tokens per session scan A 239a6e569c4f
audit is a command published in the GitHub repository lookatitude/guild (7 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 688 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.