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/embarkgit 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.00064 | $0.01034 |
| Opus 5 | $0.00032 | $0.00517 |
| Sonnet 5 | $0.00013 | $0.00207 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
embark 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/abcd:embark — unpack a lifeboat into a repo
Take a packed lifeboat (produced by /abcd:disembark) and write its record
families back into a target repository. This is the inverse of disembark and the
write half of the round-trip (adr-35): ADRs, issues, intents, and specs travel
back verbatim, the current abcd marker block is re-injected into the target
CLAUDE.md, and everything else in the lifeboat informs the report but is never
written. The target defaults to the working directory when omitted.
Probe first (read-only)
Inspect what a lifeboat would write into a target without touching either:
"${CLAUDE_PLUGIN_ROOT}/abcd" embark probe <lifeboat-dir> [target-dir] --json
The lifeboat is untrusted input: probe gates it, verifies its
manifest_sha256 against the on-disk tree, and refuses a symlink or an oversize
file anywhere inside. Then it reports:
coverage— the brief blanks and their questions, surfaced FIRST. These are what a lifeboat hands a product thinker: the sections nothing in the record could ground, each with the question a human must answer (some marked human-owned).planned— the record files that would land, each with itsfamily,target_path, andaction(createor, when the target already holds identical bytes,unchanged).conflicts— target paths that would block a write (a differing file, a non-regular target, a non-directory parent). A plan with conflicts is still a successful probe.ignored— lifeboat files not embarked (report-only,unmapped,unknown).marker— what would happen to the targetCLAUDE.mdblock.record_manifest_sha256— the record-derived closure seal.
Surface the coverage blanks to the human before anything else — they are the point of the handoff. Then summarise the plan.
Write
"${CLAUDE_PLUGIN_ROOT}/abcd" embark from <lifeboat-dir> [target-dir] --json
from runs the same planner as probe, then writes each create file into the
target through two-layer containment (an os.Root boundary plus independent
lexical validation), skipping unchanged files, and re-injects the current marker
block into the target CLAUDE.md — never foreign prose, only the canonical
block. Summarise the result: written / unchanged, the per-families counts,
and the marker action.
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 · 80 lines · 64 tokens per session scan A 9e50dba07f37
embark is a command published in the GitHub repository intentdriven/abcd (3 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,034 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.