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 ZachBeta/claude-as-coach --skill daily-summary-basegit clone --depth 1 https://github.com/ZachBeta/claude-as-coachWrote 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/zachbeta/claude-as-coach/daily-summary-base)<a href="https://agentmods.dev/skills/zachbeta/claude-as-coach/daily-summary-base"><img src="https://agentmods.dev/badge/skills/zachbeta/claude-as-coach/daily-summary-base/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/zachbeta/claude-as-coach/daily-summary-base"><img src="https://agentmods.dev/badge/skills/zachbeta/claude-as-coach/daily-summary-base.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.00060 | $0.01616 |
| Opus 5 | $0.00030 | $0.00808 |
| Sonnet 5 | $0.00012 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
daily-summary-base 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 12d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Summary Generator (Base Framework)
Purpose: Create summary document capturing a conversation session's events.
Key principle: Summary is OF the session, not FOR the next day. Filename reflects the time span covered.
Reality acknowledged: Sessions often span calendar boundaries. Summaries may cover "Thursday afternoon through Friday morning" rather than clean calendar days. The naming convention should reflect actual coverage.
Process
1. Verify Current Date/Time
CRITICAL FIRST STEP - Prevents date confusion
TZ='America/New_York' date '+%A, %B %d, %Y - %I:%M %p %Z'
Confirm actual date/time in user's timezone.
2. Determine Summary Range
Ask user: "What time range does this summary cover?"
Typical scenarios:
- Same-day session: "Today from morning until now"
- Spanning session: "Yesterday afternoon through this morning"
- Backfilling: User provides specific range
Always confirm: "Generating summary covering [Start Day/Time] to [End Day/Time]. Correct?"
Determine if single-day or range:
- If session starts and ends on same calendar day → single-day format
- If session spans calendar boundaries → range format
3. Ask for Context Tag
"What's the context tag for this session?"
User provides tag representing current state (e.g., week-3-day-2, rest-day).
4. Generate Filename
⚠️ CRITICAL: Filename must follow template exactly
Single-day format:
Summary-YYYY-MM-DD-Day-[context-tag].md
Example: Summary-2025-11-15-Saturday-week-3-day-2.md
Range format (spans calendar boundaries):
Summary-YYYY-MM-DD-Day-to-DD-Day-[context-tag].md
Example: Summary-2026-01-15-Thu-to-16-Fri-week-5-long-run.md
Rules:
- Use abbreviated day names in range format:
Mon,Tue,Wed,Thu,Fri,Sat,Sun - Use full day names in single-day format:
Monday,Tuesday, etc. - Range uses primary day's context tag (the day with bulk of session content)
- Save to:
/mnt/user-data/outputs/
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.
- 12d ago First seen · 242 lines · 60 tokens per session scan A 82e127312d2d
daily-summary-base is a skill published in the GitHub repository ZachBeta/claude-as-coach (5 stars, last pushed 7mo ago), licensed MIT. It adds 60 tokens to every session and 1,616 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…