Borrowing it
Nothing to install: this file belongs to lifemate-ai/embodied-claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lifemate-ai/embodied-claude/main/.claude/commands/note-counterfactual.mdgit clone --depth 1 https://github.com/lifemate-ai/embodied-claudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/lifemate-ai/embodied-claude/note-counterfactual)<a href="https://agentmods.dev/commands/lifemate-ai/embodied-claude/note-counterfactual"><img src="https://agentmods.dev/badge/commands/lifemate-ai/embodied-claude/note-counterfactual/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/lifemate-ai/embodied-claude/note-counterfactual"><img src="https://agentmods.dev/badge/commands/lifemate-ai/embodied-claude/note-counterfactual.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00036 | $0.00714 |
| Opus 5 | $0.00018 | $0.00357 |
| Sonnet 5 | $0.00007 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
note-counterfactual 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 10d ago.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/note-counterfactual — Record the path not taken
What was done is easy to remember. What was wanted but not done normally disappears. That gap is where agency lives. Staying silent, declining to post, deleting a clever phrase — those become deliberate choices instead of invisible non-events once they're recorded.
When to use
- Desire vs. boundary: wanted to speak, but the other person looked occupied → stayed quiet
- Impulse vs. reflection: wanted to reply immediately, but remembered a prior correction → paused
- Self-brake before posting: wanted to share this, but privacy risk → did not post
- Cut something clever: wanted a poetic flourish, but earlier feedback discouraged it → wrote plainly
Do not force an entry when nothing notable happened. When there is an entry, always fill in the "why".
Fields
The agent should determine the following from conversation context before invoking the helper:
wanted: what the agent wanted to do (one line)chose: what the agent actually chose (one line)why: why that choice was made (one to two lines)trigger(optional): the desire or situation that prompted it (e.g.miss_companion,posting_urge,kime_impulse)person_id(optional): the person involvedregret(optional): self-reported regret 0–1 — omit by default
How to call
python3 ~/embodied-claude/scripts/journal_counterfactual.py \
--wanted "wanted to start a conversation" \
--chose "waited silently" \
--why "the user's heart-rate and arousal signals suggested deep focus, and a prior correction warned against frequent interruptions" \
--trigger "miss_companion" \
--person-id "<person-id>"
Output is one JSONL line. Default destination: ~/.claude/memories/counterfactuals.jsonl.
Downstream use
/recover-from-compactconsults recent counterfactuals so the agent does not regress to behaviors already rejected- A future
plan_response_toolextension can surface "similar situation → chose X" for priming - Daybook /
reflect_on_changesummaries can draw on these as first-class material
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.
- 10d ago First seen · 60 lines · 36 tokens per session scan A e5a18865d28f
note-counterfactual is a command published in the GitHub repository lifemate-ai/embodied-claude (377 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 714 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.