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/intentgit 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.00037 | $0.02314 |
| Opus 5 | $0.00018 | $0.01157 |
| Sonnet 5 | $0.00007 | $0.00463 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
intent 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/abcd:intent — intent lifecycle
The write side of the intent record store under .abcd/development/intents/.
Every intent gets a stable itd-N id and directory-as-truth lifecycle state
(drafts/, planned/, shipped/, disciplines/, superseded/). Bare
invocation performs zero writes.
Status (bare)
"${CLAUDE_PLUGIN_ROOT}/abcd" intent --json
Summarise the JSON for the user: counts per bucket, open/closed spec counts, and the intent↔spec links. Nothing is created or moved by this invocation.
Which ledger? A half-formed observation, question, or nitpick goes to
/abcd:capture "…"; a user-facing change you want to ship goes to
/abcd:intent "…". For a big, unproven idea there is an optional third route:
/abcd:ideate runs the admission gauntlet and records the verdict either way.
It is a pointer, never a precondition — filing a draft without it is a normal
thing to do.
Decompose before filing (itd-84, hand-run)
One proposal is rarely one record. Before running the create command below, run the itd-84 decomposition as an advisory analysis the human confirms — capture routes the pieces, it never files a monolith:
- Route. Split the proposal into parts and route each to its record home — user-facing capability → an intent; trust-boundary rule → an ADR (plus a brief invariant); standing stance → a principle; plumbing → the brief. Render the result as a table: part | type | home.
- Link. Surface the existing records the proposal touches, with typed
links —
supersedes/reverses/duplicates/refines— never "related". A reversal ("this reverses invariant X") is flagged for the human to confirm, never auto-classified. - Verdict. Propose one of three outcomes — FILE-AS-IS / SPLIT / HOLD. The human adopts the routing; only the part they confirm as an intent proceeds to the create command, and the other parts go to their homes in the same session (or are captured so they are not lost).
- Grade. Append the confirmed table — and whether the initial routing
survived the human's confirmation — to the dated decomposition-calibration
note under the development record's
research/notes/. That corpus (about 50 graded captures) is what gates the automated rung.
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 · 188 lines · 37 tokens per session scan A 3cdb353cf5e0
intent is a command published in the GitHub repository intentdriven/abcd (3 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 2,314 once invoked, about $0.0002 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.