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/consultgit 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.00084 | $0.01034 |
| Opus 5 | $0.00042 | $0.00517 |
| Sonnet 5 | $0.00017 | $0.00207 |
| Haiku 4.5 | $0.00008 | $0.00103 |
Grade A, and why
consult 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Consult sources
A local-only corpus at ~/.abcd/sources/ holds source documents (working
papers, private-repo notes, PDFs, books) the agent may consult but must
never cite publicly. Metadata lives in sources.json (CSL-JSON; the
custom block carries confidential, permission_status, keywords,
aliases). Full details: ~/.abcd/sources/README.md. If the corpus is
absent, say so and stop — this command never creates it.
Hard rule (overrides convenience, always)
For any entry with custom.confidential: true: never write its title, author
names, aliases, or any identifying string into anything tracked by git or sent
anywhere external — commits, commit messages, PR/issue text, docs, code
comments, published artifacts, pasted output. This covers identifying
paraphrase too: do not describe a confidential source so specifically that a
reader could identify it ("a forthcoming paper showing X beats Y on Z", a
private repo's distinctive architecture) — the mechanical guards catch literal
strings only; this rule is the paraphrase layer. Refer generically ("a working
paper on X", "prior private work"). The ledger holds the real reference;
citation is the user's manual decision, made when permission exists (public
citation requires BOTH the source's permission_status AND the ledger line's
cited_publicly flag).
Conversation with the user is fine — discuss confidential sources freely there.
Consult
- Search the corpus:
grep -ril "<term>" ~/.abcd/sources/confidential/ ~/.abcd/sources/public/— try keywords, author surnames, and CSL keys. The path IS the classification: any hit underconfidential/falls under the hard rule above. Each source is a folder (<class>/<key>/) holdingoriginal.<ext>,text.md, and any summaries/notes. - Read matched files freely for conversation; the folder's class governs what may leave it.
- If nothing relevant surfaces, say so — do not pad.
To add a source, use /abcd:ingest.
Record influence (the ledger)
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 · 81 lines · 84 tokens per session scan A 1116c0882c13
consult is a command published in the GitHub repository intentdriven/abcd (3 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 1,034 once invoked, about $0.0004 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.