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/tdwhere123/do-it/do-it-decidenpx skills add tdwhere123/do-it --skill do-it-decidegit clone --depth 1 https://github.com/tdwhere123/do-itWrote 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/tdwhere123/do-it/do-it-decide)<a href="https://agentmods.dev/skills/tdwhere123/do-it/do-it-decide"><img src="https://agentmods.dev/badge/skills/tdwhere123/do-it/do-it-decide.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 | $0.00040 | $0.01006 |
| Opus 5 | $0.00020 | $0.00503 |
| Sonnet 5 | $0.00008 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
do-it-decide 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 today.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Do-It Decide
Decide before building only where a wrong decision is expensive. Do not spend
more cognition than the decision is worth (core §r-route).
Leading words: decision surface, cheapest resolver, decision boundary, readiness.
Bounded reversible work with the route already determined: inspect, act, check. Do not manufacture a plan file, interview, or worker.
1. Find the decision-changing unknown
State the outcome and the one uncertainty that can change scope, user-visible
behavior, authority, reversibility, or proof. Read facts; do not ask the user
for information the environment can provide (core §r-evidence).
When the user may not know what to consider, run a brief blind-spot pass.
When they can recognize but not verbalize the answer, use a reference,
materially different options, or the cheapest useful prototype — not an
interview. Unknown types: decision-resolvers.md.
2. Cheapest reliable resolver
Use the cheapest reliable resolver: repo evidence → reference → one user decision → research → experiment/prototype → at most one fresh-context second look. Subagents are last, not default.
Ask one question at a time; wait for the answer. Each question: 2–3 options
that differ on a load-bearing axis, tradeoffs, recommended default. If the user
cannot evaluate the options, teach the real trade-off and recommend a default;
do not extract a guess (core §r-uncertainty).
3. Dominant route or decision boundary
Do not generate cosmetic variants. Alternatives must differ on a load-bearing axis: framing, seam, authority, flow, dependency, reversibility, optimization target, or scope.
If one route satisfies every must with less concept growth and no hidden caller cost, choose it. Otherwise state the decision boundary: the fact under which each viable route wins. Do not average two live routes into a hybrid score.
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.
- today Changed · +38 lines · -2 tokens per session 16abd2a5101f
- 4d ago First seen · 64 lines · 42 tokens per session scan A 4b0a0c67c4db
do-it-decide is a skill published in the GitHub repository tdwhere123/do-it (27 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 1,006 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 skills, from other repositories
deploy
Use when shipping a release of Agent Sessions — bumping version, updating CHANGELOG, building, signing, notarizing, publishing appcast, and creating a GitHub release.
release-notes
Use when writing or curating the user-facing release copy for an Agent Sessions release — README "What's New", GitHub release notes, Sparkle release notes, or website/launch copy. Not for the internal CHANGELOG, which stays a full development history.
sc-skill
Capture deterministic macOS screenshots for testing, docs, release notes, and marketing assets. Use when asked to automate app screenshots, batch-generate screenshot sets, standardize window sizing/composition, or choose between Peekaboo and native macOS screenshot tooling.
add-agent-support
Create and ship AgentSessions support for a new or changed local AI agent/provider. Use when adding, reviewing, testing, documenting, or marketing a provider integration, session parser, transcript source, support-matrix entry, verified-version bump, or provider UI surface; drives the full loop from pre-support…
handover
Use when wrapping up or capturing the current state of a coding session — writes a short, dated entry to the repo's RepoHandover.md so a future agent or you can resume without grepping archived sessions. Triggers on "handover", "hand off", "write handover", "capture state", "checkpoint this session".
agent-session-format-check
Verify agent session format compatibility for Agent Sessions. Use when any agent CLI updates, when monitoring flags drift, or when bumping max verified versions (fixtures + docs + tests). Covers session schema, usage/limits tracking, storage backends, and discovery path contracts for all supported agents.