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/lintgit 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.00056 | $0.00695 |
| Opus 5 | $0.00028 | $0.00347 |
| Sonnet 5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
lint 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:lint repo-conformance check
Run the abcd binary's read-only conformance lint for the current repo and
present the result. This command performs zero writes — it reports gaps, it
never fixes them (remediation stays with /abcd:prepare-this-repo).
Run:
"${CLAUDE_PLUGIN_ROOT}/abcd" lint --json
Then summarise the JSON for the user. Its shape is { "findings": [ … ], "skipped": [ … ] }:
findings— each has a stableruleId, aseverity(errororwarn), afile, alineon content-scanning findings only (docs-currency,privacy-hygiene,identity-positioning— path-presence findings omit the key entirely), amessage, and afix. Group them by severity: reporterrorfindings first (these fail conformance), thenwarnfindings (advisory). For each, give thefile(with:linewhen present), themessage, and thefix.skipped— rule ids that did not apply to this repo (e.g.docs-currencywhen there is nodocs/). Mention them as "not applicable", not as failures.
State the outcome plainly: if there are no findings the repo conforms; otherwise
lead with how many errors and warnings there are. The process exit code is the
Conftest tri-state — 0 clean, 1 warnings only, 2 any error — so
abcd lint can also gate a repo's CI.
A privacy-hygiene finding on a deliberately illustrative line can be waived by
adding abcd-lint:allow on that line (the earlier abcd-audit:allow spelling is
honoured too). No other rule honours that marker: a docs-currency finding takes
the docs-lint engine's own <!-- docs-lint: allow --> escape, and the remaining
rules have no line waiver — resolve what they report.
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 · 53 lines · 56 tokens per session scan A fab981fbdbfe
lint is a command published in the GitHub repository intentdriven/abcd (3 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 695 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.