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-verifynpx skills add tdwhere123/do-it --skill do-it-verifygit 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-verify)<a href="https://agentmods.dev/skills/tdwhere123/do-it/do-it-verify"><img src="https://agentmods.dev/badge/skills/tdwhere123/do-it/do-it-verify.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.00049 | $0.00906 |
| Opus 5 | $0.00024 | $0.00453 |
| Sonnet 5 | $0.00010 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
do-it-verify 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Do-It Verify
Evidence before status. This skill is the universal checklist; host hooks may block, remind, or be unavailable. Never let a hook substitute for claim-specific proof.
Leading words: fresh evidence, this worktree, acceptance map, claim.
Before Any Done Claim
Closeout is an acceptance→evidence map (core §r-verify). Observed event ≠
proof. Ledger rows, old CI, worker summaries, and memory are candidates, not
closeout.
If there is no durable contract, extract a minimal acceptance from the user
ask and current Goal; do not stall for a file
(../references/task-contract.md).
Prefer checks that hit the changed surface after the last edit on this worktree.
Cannot Be VERIFIED
These cannot support VERIFIED, even when a command exited 0:
- stale — evidence predates the last edit
- other worktree — not this worktree / HEAD / fingerprint
- irrelevant — green on a different surface than the claim
- mock-only — synthetic collaborator chain; live path unproven
- partial — some acceptance items unmapped, or the check is incomplete
Honest NOT_VERIFIED names the missing proof and the next check.
Closeout
Claim
Contract / task
Worktree + HEAD/fingerprint if known
Acceptance map:
A1 → evidence E...
A2 → NOT_VERIFIED / missing <check>
Review state
Residual risk
Deferred / reinterpreted items
VERIFIED | FAILED | NOT_VERIFIED
Overall VERIFIED is illegal unless every material acceptance item maps to
fresh, relevant, this-worktree, non-mock-only, non-partial evidence. FAILED
means evidence disproves the claim. Missing or incomplete proof is
NOT_VERIFIED, not FAILED.
For each mapped item, say why that evidence is relevant, that it ran after the last change, that it is from this worktree, and that it is not mock-only. Production claims need production-side evidence.
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 · +51 lines · +3 tokens per session 5c6e0bce8e12
- 4d ago First seen · 53 lines · 46 tokens per session scan A 1e96676c27be
do-it-verify is a skill published in the GitHub repository tdwhere123/do-it (27 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 906 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.