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 skills add michaeljauk/brain-starter --skill log-decisiongit clone --depth 1 https://github.com/michaeljauk/brain-starterWrote 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/skills/michaeljauk/brain-starter/log-decision)<a href="https://agentmods.dev/skills/michaeljauk/brain-starter/log-decision"><img src="https://agentmods.dev/badge/skills/michaeljauk/brain-starter/log-decision.svg" alt="Measured on agentmods" 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.00022 | $0.00177 |
| Opus 5 | $0.00011 | $0.00088 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
log-decision 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 6d 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.
What it actually says
Log Decision
Capture non-trivial decisions that span projects, with context and alternatives considered.
Trigger phrases
- "log decision: [topic]"
- "/log-decision [topic]"
Workflow
- Ask for context if not provided (what needed deciding, who was involved, alternatives considered)
- Create
decisions/YYYY-MM-DD-short-slug.mdusing the template indocs/templates.md - Use today's date
Scope
Business, product, hiring, vendor, cross-project architecture.
Not product or tech ADRs — those live in the product repo at /docs/adr/.
Not project-specific decisions — those go in projects/{project}/decisions/.
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.
- 6d ago First seen · 27 lines · 22 tokens per session scan A d5e4f4063945
log-decision is a skill published in the GitHub repository michaeljauk/brain-starter (5 stars, last pushed 10d ago), licensed MIT. It adds 22 tokens to every session and 177 once invoked, about $0.0001 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 skills, from other repositories
triage-tasks
Use when you want to review and batch-update open vault task statuses for the current project or across all projects.
tackle-task
Use when starting work on a specific vault task, when a task title or path is mentioned, or when coming from triage output.
add-task
Use when you want to quickly capture a new task in the vault from a title, with optional priority and due date.
project-creator
A project setup process that creates a new project in a vault with planning, task, context, log, and README files, and updates project indexes.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.