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 moonxorsun/focus-claude-code --skill donegit clone --depth 1 https://github.com/moonxorsun/focus-claude-codeWrote 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/moonxorsun/focus-claude-code/done)<a href="https://agentmods.dev/skills/moonxorsun/focus-claude-code/done"><img src="https://agentmods.dev/badge/skills/moonxorsun/focus-claude-code/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/moonxorsun/focus-claude-code/done"><img src="https://agentmods.dev/badge/skills/moonxorsun/focus-claude-code/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.00016 | $0.01399 |
| Opus 5.5 | $0.00006 | $0.00560 |
| Sonnet 5.5 | $0.00003 | $0.00280 |
| Haiku 4.5 | $0.00002 | $0.00140 |
Grade A, and why
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 2mo 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment
| Variable | Default |
|---|---|
CLAUDE_FOCUS_DIR |
.claude/tmp/focus |
Use $CLAUDE_FOCUS_DIR in paths. If unset, use the default .claude/tmp/focus.
Focus Session Completion Workflow
Execute this workflow when user invokes /focus:done.
Step 1: Run Focus Done Script
python "{{FOCUS_PLUGIN_ROOT}}/scripts/focus_done.py"
The script will:
- Checkpoint: Process all unprocessed sessions (errors → pending_issues.md, omissions → detected)
- Extract: Parse focus_context.md — table items (fast path) and
##sections (fallback) - Archive Suggestions: Group table items by Category, or list section summaries with suggested categories
- Pending Issues: Group by tool/pattern for analysis
- Output [REQUIRED]: Instructions for you to follow
Step 2: Archive Findings
Follow the [REQUIRED] instructions from script output.
Archive Flow
For each archive batch:
- Call AskUserQuestion with options: Accept / Edit destinations / Skip
- If accepted, write items to target file (see Archive Format in Reference)
- If target is directory, scan for best matching file
- If file doesn't exist and
auto_create_missing_files: false, ask user
Section-based Archive (Fallback)
When the script outputs section summaries instead of table batches (because focus_context.md uses free-form content rather than standard tables), follow this flow:
- Read focus_context.md to get the full content of each listed section
- For each section, judge whether the content is worth archiving
- Use the
suggested categoriesfrom script output to map to archive targets in config - If no category is suggested or you're unsure about the destination, call AskUserQuestion to confirm with the user
- Write content in a format appropriate for the target document (tables, headings, lists, etc.)
Bug Fixes (Special Handling)
For each bug fix found in the session, evaluate:
| Criteria | Question |
|---|---|
| Easily triggered? | Could this happen again in normal development? |
| Hard to diagnose? | Did it take 2+ attempts to find root cause? |
| Non-obvious fix? | Would another developer struggle with this? |
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.
- 2mo ago First seen · 184 lines · 16 tokens per session scan A c80d9084a1ce
done is a skill published in the GitHub repository moonxorsun/focus-claude-code (5 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 1,399 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.