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/identitygit 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.00061 | $0.01066 |
| Opus 5 | $0.00030 | $0.00533 |
| Sonnet 5 | $0.00012 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
identity 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/abcd:identity repo positioning
A project's positioning fragments silently: the README strapline, the package or plugin manifest description, and the conventions file's opening line are each edited at different moments, until three surfaces tell three stories. This command shows the one canonical identity block the repo records, and which surfaces still say it.
Bare — what this repo says about itself
"${CLAUDE_PLUGIN_ROOT}/abcd" identity --json
emits { "block": …, "severity": …, "surfaces": [ … ] }:
block— the canonicaltitle,tagline, and optionalpitch, plus thefileandlinethey are recorded at.severity— the family's weight,warn(the default) orblocker.surfaces— one entry per registered surface: itsid, thefileandlinechecked, and astatusofok,drifted,absent(no such file in this repo — not a fault), orunlocatable(the file is there but the locator matches nothing, so drift would go unseen). Adriftedentry carriesfound(the exact text the surface says),missing(which block fields it no longer carries), andcanonical(what the block says it should).
Report the block first, then any surface that is not ok, naming the file, the
line, what it says, and what the block says. It exits 0 even when it reports
drift: this form is a status render, and the gate is abcd lint.
render — the proposed correction
"${CLAUDE_PLUGIN_ROOT}/abcd" identity render
prints a unified diff per drifted surface. It writes nothing, and no flag makes it: adopting a proposal is the maintainer's move. Show the diff, then ask whether to apply it. If the maintainer would rather change what the project says than what its surfaces say, the fix is an edit to the identity block, after which this same command chases the surfaces.
init — record the block
Run this only as part of onboarding a repo, and only after the interview below.
"${CLAUDE_PLUGIN_ROOT}/abcd" identity init --title "…" --tagline "…" [--pitch "…"] [--file <path>] [--heading <text>]
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 · 91 lines · 61 tokens per session scan A d30a2b90c803
identity is a command published in the GitHub repository intentdriven/abcd (3 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 1,066 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.