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 michal-bajer1/shadow --skill capture-decisiongit clone --depth 1 https://github.com/michal-bajer1/shadowWrote 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/michal-bajer1/shadow/capture-decision)<a href="https://agentmods.dev/skills/michal-bajer1/shadow/capture-decision"><img src="https://agentmods.dev/badge/skills/michal-bajer1/shadow/capture-decision/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/skills/michal-bajer1/shadow/capture-decision"><img src="https://agentmods.dev/badge/skills/michal-bajer1/shadow/capture-decision.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.00014 | $0.01278 |
| Opus 5 | $0.00007 | $0.00639 |
| Sonnet 5 | $0.00003 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
Grade A, and why
capture-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 9d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before this commit is finalised, follow these steps in order.
Step 1 — Discover staged files
Run:
git diff --cached --name-only git diff --cached --stat
Group the staged files by logical decision. Files that implement one independent design choice are one decision. Files in different areas with separate design choices are separate decisions — run shadow-cli record once per decision.
Which files to include in --paths:
Include files where the decision lives — where the core logic, resource declaration, or configuration choice is expressed. Exclude files that only reference, surface, or test the decision.
Examples across different artifact types:
Code: Include: src/payments/handler.go (core logic), src/auth/middleware.ts Exclude: src/payments/handler_test.go, src/index.ts (re-exports only)
Infrastructure (Terraform): Include: terraform/modules/container-apps/main.tf (resource declaration) Exclude: terraform/modules/container-apps/outputs.tf (attribute exposure only) Prefer --dirs terraform/modules/container-apps when the decision spans the module
Infrastructure (Kubernetes): Include: k8s/apps/payments/deployment.yaml Prefer --dirs k8s/apps/payments when the decision is about the whole application
Scripts and CI: Include: scripts/migrate.sh, .github/workflows/deploy.yml Exclude: scripts/helpers.sh if it is a generic utility with no design decisions
Cloudflare Workers: Include: cloudflare/workers/auth/index.js (worker logic) Prefer --dirs cloudflare/workers/auth when the decision spans worker + config
DNS / zone files: Include: dns/zones/example.com.zone (the zone declaration)
Use --dirs instead of --paths when the decision is about the directory as a whole (a module, a service, an application) rather than a specific file. Use both when the decision is file-specific but you also want the directory structure tracked for drift.
Step 2 — Resolve drifted decisions in scope
For each affected directory, run:
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.
- 9d ago First seen · 145 lines · 14 tokens per session scan A 72bd441fbe90
capture-decision is a skill published in the GitHub repository michal-bajer1/shadow (2 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 1,278 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…