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/alphabravo-oss/guild/plangit clone --depth 1 https://github.com/alphabravo-oss/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.00010 | $0.12514 |
| Opus 5 | $0.00005 | $0.06257 |
| Sonnet 5 | $0.00002 | $0.02503 |
| Haiku 4.5 | $0.00001 | $0.01251 |
Grade B, and why
plan scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- NO Bash tool calls — do not run any commands How it starts
The opening of the file, as written. The whole thing — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Plan Command
Execute the setup script to initialize the research + interview session:
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-forge.sh" $ARGUMENTS
You are now conducting a codebase-aware specification interview. Follow the instructions provided by the setup script exactly.
MODE DETECTION (R-pre)
Before R0, detect which pipeline this run uses. Three modes:
| Mode | When | Pipeline |
|---|---|---|
brownfield |
existing codebase, flow-shaped request | V3: flow-mapper → flow-interviewer → flow-delta.json (plus spec.md for compatibility) |
greenfield |
empty or near-empty target, flow-shaped request | V2 pipeline unchanged (end-state-first is correct when there is no upstream to honor) |
cosmetic |
non-flow-shaped request (styling, copy, deps, docs, minor refactor) in any codebase | V2 pipeline, no flow mapping |
Detection procedure:
- If
--brownfield,--greenfield, or--cosmeticflag was passed → use that mode verbatim. Skip auto-detection. - Otherwise, auto-detect:
- Count relevant-language source files under target paths (Go
*.go, TS/JS*.ts|*.tsx|*.js|*.jsx, Python*.py, Rust*.rs, excluding tests, vendored code,node_modules/).find "${PROJECT_ROOT}" -type f \( -name "*.go" -o -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" -o -name "*.py" -o -name "*.rs" \) \ -not -path "*/vendor/*" -not -path "*/node_modules/*" -not -path "*/target/*" -not -path "*/__pycache__/*" \ -not -name "*_test.go" -not -name "*.test.ts" -not -name "*.test.tsx" -not -name "*.spec.ts" \ | wc -l - If count ≤ 20 → default
greenfield. - Else → read the user's feature-name / initial prompt. If the request is flow-shaped (adds a new feature, new endpoint, new page, new data flow, new module) → default
brownfield. If it is cosmetic (styling, copy edit, README update, dependency bump, minor refactor with no behavioral change) → defaultcosmetic.
- Count relevant-language source files under target paths (Go
- Confirm with the user via AskUserQuestion — always. Show the detected mode, the file count, and a one-line rationale. Options:
confirm|force-greenfield|force-brownfield|force-cosmetic|abort. - Record the chosen mode to
state.mdasmode: brownfield|greenfield|cosmeticbefore proceeding.
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 · 515 lines · 10 tokens per session scan B d90d34385455
plan is a command published in the GitHub repository alphabravo-oss/guild (2 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 12,514 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). 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.