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/intentdriven/abcd/updategit clone --depth 1 https://github.com/intentdriven/abcdWhat 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.00052 | $0.00709 |
| Opus 5 | $0.00026 | $0.00354 |
| Sonnet 5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
update 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 yesterday.
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.
What it actually says
/abcd:update
Complete a chosen update of the PATH-installed binary. The verb's documented
meaning IS the fetch: it resolves the latest release (or takes an explicit
tag), verifies the platform binary against the same release's
checksums.txt, and swaps the PATH copy atomically, printing a receipt with
the origin, tag, digest, and old→new versions. abcd never checks for or
applies updates on its own — this verb, and version --check, are the only
two commands that reach the release origin, and each only when invoked.
Run:
"${CLAUDE_PLUGIN_ROOT}/abcd" update --yes --json
An explicit tag pins the release; the bare form resolves the latest and the
receipt names what it resolved (--yes skips the terminal confirmation,
which cannot be answered here):
"${CLAUDE_PLUGIN_ROOT}/abcd" update v0.7.0 --json
Report the receipt's action, tag, digest, target_path, and
old_version → new_version from the JSON. If env_ignored is present,
relay it — it names proxy/CA environment overrides the fetch deliberately
refused to honour.
Expect a refusal in a plugin session, and relay it as the answer, not an
error. Every refusal is a named shape with a remedy in refusal:
plugin-root— the binary belongs to the plugin install, andabcd updatenever touches a plugin root. Tell the user to take a plugin update in the host.dev-shim— the PATH entry is the track-latest dev shim;abcd ahoy installswitches modes first.owned-dangling— a plugin update stranded the entry;abcd ahoy installrepoints it.package-manager— the binary resolves into a Homebrew Cellar; relay the printedbrew upgrade abcd.foreign/unprovenanced-file— abcd never clobbers a binary it cannot prove is its own; relay the described occupant and remedy.absent— nothing on PATH to update; point at the install remedy.
Binary resolution. Run "${CLAUDE_PLUGIN_ROOT}/abcd" — a plugin install
provisions the binary into the plugin root, so this is the rung that fires for a
plugin user. If that path does not exist, try abcd on PATH; if that fails
too, you are in a source checkout of this repo, where — and only there —
go run ./cmd/abcd works, the published payload carrying no cmd/. To put a
binary on PATH, run ahoy install through whichever rung just resolved:
"${CLAUDE_PLUGIN_ROOT}/abcd" ahoy install, abcd ahoy install, or
go run ./cmd/abcd ahoy install in a source checkout.
User input: $ARGUMENTS
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.
- yesterday First seen · 62 lines · 52 tokens per session scan A 10d7eb240083
update is a command published in the GitHub repository intentdriven/abcd (3 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 709 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
legal
Primary entry point for all BetterCallClaude requests — classifies intent, resolves jurisdiction (via swiss-legal-research), runs inline briefing for complexity 4–6, activates full briefing session when complexity ≥ 7 (via legal-intake skill), and routes to specialist agents or workflow pipelines. Invoked explicitly…
briefing
Structured pre-execution briefing session -- collects case context through specialist panel, builds execution plan, supports resume and depth control.
help
Show complete BetterCallClaude command reference, available agents, skills, and usage examples.
legal-5step
Execute the BetterCallClaude 5-step Swiss legal framework: intake → research → strategy → adversarial → draft. A complete end-to-end pipeline for any Swiss legal matter, from document analysis through final legal output.
legal-loop
Iterate a worker-evaluator cycle against a Goal Record until the success condition is met or a stop limit is reached. The evaluator (a different agent than the worker) judges each iteration using MCP verification tools. Produces an auditable verdict trail and a final MET / NOT MET status.
workflow
Define and execute multi-agent legal workflows -- due diligence, litigation prep, contract lifecycle, real estate closing.