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 t0ddharris/claude-code-skills --skill startgit clone --depth 1 https://github.com/t0ddharris/claude-code-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/t0ddharris/claude-code-skills/start)<a href="https://agentmods.dev/skills/t0ddharris/claude-code-skills/start"><img src="https://agentmods.dev/badge/skills/t0ddharris/claude-code-skills/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/t0ddharris/claude-code-skills/start"><img src="https://agentmods.dev/badge/skills/t0ddharris/claude-code-skills/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.00038 | $0.00819 |
| Opus 5.5 | $0.00015 | $0.00328 |
| Sonnet 5.5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Start
Run this at the beginning of every new session. It gives you and the user a shared understanding of where things left off and what's in play.
Steps
1. Read the Session Brief
Read brief/session-brief.md in full. This is the primary source for what happened last session, what decisions were made, and what's still open.
2. Check Git Status
Run git status and git log --oneline -5 to see:
- Any uncommitted changes from the last session
- The most recent commits for context
2.5. Sync Skills to .agents/ (opt-in projects only)
If the project has an .agents/ directory, run the project-level sync from the sync-skills skill (hardlink .claude/skills/ → .agents/skills/). Do not prompt for scope — project only. Only mention it if something was added or removed.
If there is no .agents/ directory, skip silently — never create one. To opt a project in, run /sync-skills once manually and add .agents/ to its .gitignore.
3. Check the Date
Note the current date and compare it to the session brief date. If significant time has passed (more than a few days), flag it — some carryover items may be stale or already handled.
4. Deliver the Session Summary
Output a concise summary for the user with these sections:
## Session [N+1] — [Current Date]
### Last Session Recap
[2-3 sentence summary of what happened]
### Open Items
[Bulleted list of carryover tasks, prioritized by urgency/relevance]
### Uncommitted Changes
[List any uncommitted files, or "Clean working tree" if none]
### Ready when you are.
Keep it tight. The user has already read the brief if they want detail — this is the quick orientation.
5. Increment the Session Number
Note the new session number based on the brief's session number. When the user runs /brief at the end of this session, use the incremented number.
Rules
- Do NOT modify any files during /start — this is read-only, except the skills sync (step 2.5)
- Do NOT start working on carryover items automatically — wait for the user to direct
- Do NOT push the user toward the next topic while they're still working through the current one — wait for them to signal they're ready to move on
- If the brief is missing or empty, say so and ask the user what they'd like to work on
- If there are uncommitted changes, mention them but don't commit — the user decides
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.
- 1mo ago First seen · 73 lines · 38 tokens per session scan A c021631112e5
start is a skill published in the GitHub repository t0ddharris/claude-code-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 819 once invoked, about $0.0002 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
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.
baoyu-diagram
Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
spring-boot-team-harness
Adds a shared agent harness to a Maven Spring Boot 4 project so every teammate's Claude Code or Codex session works under the same rules. It writes AGENTS.md (read by both tools), a committed .claude/settings.json, ./mvnw verify gates that fail on null-safety bugs (NullAway with JSpecify), module-boundary breaches…
playwright-frontend
For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable data-testid attributes (naming convention, uniqueness in lists, stability rules) for React…