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 startgit 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/start)<a href="https://agentmods.dev/skills/moonxorsun/focus-claude-code/start"><img src="https://agentmods.dev/badge/skills/moonxorsun/focus-claude-code/start/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/start"><img src="https://agentmods.dev/badge/skills/moonxorsun/focus-claude-code/start.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.00032 | $0.01133 |
| Opus 5.5 | $0.00013 | $0.00453 |
| Sonnet 5.5 | $0.00006 | $0.00227 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
start 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 — 165 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.
Single-File Planning
Use a single persistent markdown file as your "working memory on disk."
Quick Start
-
Check for existing session (use Glob):
- If
.claude/tmp/focus/focus_context.mdexists → Ask user: "Found existing focus session. Continue it (use/focus:recover), or start fresh?" - If not found → Proceed
- If
-
Ensure directory exists:
mkdir -p .claude/tmp/focus -
Create
.claude/tmp/focus/focus_context.mdusing template below -
Update after each phase — Mark complete, record valuable information
See examples.md for template examples.
Template
# Focus: [short title]
## Task
[Brief description of what we're trying to accomplish]
## Plan
- [ ] Phase 1: ...
- [ ] Phase 2: ...
- [ ] Phase 3: ...
Optional sections — add any ## Section freely. Common examples:
## Findings
[Architecture patterns, conventions, external knowledge, techniques discovered]
## Issues
[Bugs encountered, root causes, resolutions]
## Decisions
[Design decisions with rationale, approach trade-offs]
Format within sections is free — use tables, lists, prose, whatever fits. The /focus:done workflow detects all ## sections and suggests archive destinations.
Category Reference
These categories guide what information is worth recording, and map to /focus:done archive targets:
| Category | What to record |
|---|---|
| architecture | Patterns, structures, component design |
| bugs | Unresolved bugs, known issues |
| resolved_bugs | Fixed bugs with root cause and solution |
| troubleshooting | Debugging processes, diagnostic steps |
| conventions | Coding standards, naming rules |
| external_knowledge | External references, API docs, libraries |
| techniques | Implementation techniques, algorithms |
| decisions | Design decisions, architectural choices |
| config | Build system, configuration settings |
| ai_norms | AI collaboration rules, behavioral norms |
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.
- 2mo ago First seen · 165 lines · 32 tokens per session scan A e5e9888f16e5
start is a skill published in the GitHub repository moonxorsun/focus-claude-code (5 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 1,133 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.