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 AfterRealm/father-time --skill daily-briefgit clone --depth 1 https://github.com/AfterRealm/father-timeWrote 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/afterrealm/father-time/daily-brief)<a href="https://agentmods.dev/skills/afterrealm/father-time/daily-brief"><img src="https://agentmods.dev/badge/skills/afterrealm/father-time/daily-brief/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/afterrealm/father-time/daily-brief"><img src="https://agentmods.dev/badge/skills/afterrealm/father-time/daily-brief.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.00071 | $0.00505 |
| Opus 5 | $0.00036 | $0.00253 |
| Sonnet 5 | $0.00014 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
daily-brief 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 11d 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.
What it actually says
Daily Briefing
Provide a concise start-of-day briefing to help the user plan their Claude Code usage.
What to Include
1. Time Check
- Current time in user's timezone
- What day of the week it is
- Weekend or weekday
2. Peak Hour Status
- Are we currently in peak hours?
- When does the next peak window start/end?
- Optimal work windows for today
3. Schedule Outlook
Weekday template:
Today's Peak: [start] – [end] in your timezone
Right now: [PEAK/OFF-PEAK]
Best heavy-work windows: Before [peak start] and after [peak end]
Weekend template:
No peak throttling today. Work freely all day.
4. Activity Pattern Insight
Read ${CLAUDE_PLUGIN_DATA}/activity_patterns.json and note:
- "You typically start around [time] on [weekday]s"
- "You've been averaging [N] sessions per week"
- Any notable patterns (night owl, morning person, weekend warrior)
5. Work Recommendation
Based on current time + peak status:
- If it's pre-peak: "You have [N hours] before peak starts. Good time for heavy work."
- If it's peak: "Peak hours active. Light work recommended, or wait [N hours] for off-peak."
- If it's post-peak: "Peak is over. Clear for heavy work until tomorrow."
- If it's late night: "Deep off-peak. Best time for marathon sessions."
Response Format
Keep it tight — this should be a quick glance, not a report:
Good [morning/afternoon/evening]. [Day], [Date].
[PEAK/OFF-PEAK] — [status detail]
Heavy work window: [optimal times]
You usually work [pattern insight].
[One-line recommendation]
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.
- 11d ago First seen · 66 lines · 71 tokens per session scan A b4dd11683d0a
daily-brief is a skill published in the GitHub repository AfterRealm/father-time (6 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 505 once invoked, about $0.0004 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.