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 adamlinscott/claude-skills --skill are-we-donegit clone --depth 1 https://github.com/adamlinscott/claude-skillsWrote 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/adamlinscott/claude-skills/are-we-done)<a href="https://agentmods.dev/skills/adamlinscott/claude-skills/are-we-done"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/are-we-done/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/adamlinscott/claude-skills/are-we-done"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/are-we-done.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.00203 | $0.01936 |
| Opus 5 | $0.00102 | $0.00968 |
| Sonnet 5 | $0.00041 | $0.00387 |
| Haiku 4.5 | $0.00020 | $0.00194 |
Grade A, and why
are-we-done 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
are-we-done
Answer one question — can this session close? — and answer it the same way every time.
Done does not mean everything is finished. It means nothing is still undecided: every open point has been settled as done, won't do, deferred, or another session's work. An item parked with a reason is closed. An item nobody ruled on is not, however small.
Read-only. This skill never edits, commits, or fixes, and never decides on the user's behalf.
1. Sweep (all six, in order, every run)
Run the full sweep before judging anything — see REFERENCE.md for the exact commands and what counts as a hit.
- Todo list — any item not
completed. - This session's own promises — "I'll do X next", "leaving Y for now", "we should also Z", plus any question you put to the user that never got an answer. If the session was compacted or you cannot see its start, that is itself a hit — an empty result from a transcript you can only half-read is not a clean leg, and reporting it as one is inventing closure.
- Work tree —
git status: uncommitted edits, untracked files, conflict markers, a half-applied multi-file change, an in-progress merge or rebase. - Markers introduced by this work —
TODO/FIXME/XXX/HACKadded by this session, in unstaged, staged and committed changes; a committed-only sweep misses exactly the markers written last. An empty commit range is a range that did not resolve, not a clean sweep. Pre-existing markers elsewhere in the repo are not this session's business. - Verification state — did tests, typecheck, lint, or build run after the last edit, and what did they say? Never assume; if nothing ran since the last change, that is an open point.
- Referenced work items — every issue, ticket, or PR number named this session, resolved to
its title (
gh issue view <n> --json title, or the tracker's equivalent). A bare number never appears in the output. Unresolvable → use the title as stated this session, marked(unverified); a missingghis an environment gap, not an undecided point.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · +4 tokens per session 195d507f921a
- 11d ago First seen · 116 lines · 199 tokens per session scan A f8f9fc59c6da
are-we-done is a skill published in the GitHub repository adamlinscott/claude-skills (3 stars, last pushed today), licensed MIT. It adds 203 tokens to every session and 1,936 once invoked, about $0.0010 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
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-ref-git-workflow
Git workflow patterns, branch strategies, conventional commits, and PR templates reference for git operations. Agent-extending skill that amplifies manager-git expertise with production-grade git workflow patterns. NOT for: code implementation, testing, architecture design, documentation content.
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
commit-and-push
Create a well-formatted git commit and push to remote repository.
steward-prep-delivery
Steward-assisted prep for filing issues and PRs — environment capture, template selection, duplicate detection, delivery-policy compliance check.