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 skills/teejayen/arc/decision-capturenpx skills add teejayen/arc --skill decision-capturegit clone --depth 1 https://github.com/teejayen/arcWhat 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.00414 |
| Opus 5 | $0.00018 | $0.00207 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
decision-capture 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 3d 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
Decision Capture
Extract and document a decision from the conversation.
When to Use
- A clear decision has been made during conversation
- User wants to record reasoning for future reference
- Trade-offs were weighed and a choice was made
Execution Steps
Step 1: Get date
date "+%Y-%m-%d"
Step 2: Identify the decision
If not clear from context, ask which decision to capture.
Step 3: Create decision file
Location: decisions/YYYY-MM-DD-decision-topic.md
---
title: "Decision: [Clear title]"
created: YYYY-MM-DD
tags: [decision, relevant-area]
status: active
---
# Decision: [Clear title]
**Date:** YYYY-MM-DD
**Area:** [Which life domain - career, projects, family, etc.]
## The Decision
[Clear statement of what was decided]
## Context
[What situation led to needing this decision]
## Options Considered
### Option 1: [Name]
[Description]
- Pros: ...
- Cons: ...
### Option 2: [Name]
[Description]
- Pros: ...
- Cons: ...
## Why This Option
[The reasoning and trade-offs that led to this choice]
## Implications
- What this means for...
- Changes to...
## Success Criteria
[How we'll know it was the right call]
## Review
[When to revisit - "in 3 months", "after X happens", or "no review needed"]
## Related
- [[session-file-if-applicable]]
- [[related-notes]]
Step 4: Confirm
- Confirm the file location
- Remind that
/sessionwill push to GitHub
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.
- 3d ago First seen · 84 lines · 37 tokens per session scan A 2963cecd85f8
decision-capture is a skill published in the GitHub repository teejayen/arc (5 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 414 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…