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 agentmods add skills/garrytan/gbrain/daily-task-prepnpx skills add garrytan/gbrain --skill daily-task-prepgit clone --depth 1 https://github.com/garrytan/gbrainWrote 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/garrytan/gbrain/daily-task-prep)<a href="https://agentmods.dev/skills/garrytan/gbrain/daily-task-prep"><img src="https://agentmods.dev/badge/skills/garrytan/gbrain/daily-task-prep.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00440 |
| Opus 5 | $0.00016 | $0.00220 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
daily-task-prep 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 4d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- daily-task-prep — 88% identical, 2 lines differ
- daily-task-prep — 88% identical, 2 lines differ
What it actually says
Daily Task Prep
Contract
This skill guarantees:
- Calendar/meetings for today are loaded with brain context per attendee
- Open threads from yesterday are surfaced
- Active tasks reviewed with priority ordering
- Prep briefing is actionable (not just informational)
Phases
- Load calendar. Check today's meetings. For each: load attendee brain pages, recent timeline, open threads.
- Check yesterday's threads. When google sources exist,
gbrain waiting --jsonis the real data source for open threads and unanswered items — prefer it over prose heuristics (it carries loop rows with counterparty, due date, and evidence; seeskills/google-loops/SKILL.md). Otherwise, search brain for yesterday's timeline entries. Flag anything unresolved. - Review active tasks. Load
ops/tasksfrom brain. Surface P0 and P1 items. - Compile prep briefing. Per-meeting context cards + open threads + task priorities.
Output Format
Morning Prep — {date}
======================
Meetings today: {N}
## {Meeting 1 title} at {time}
Attendees: {names with brain context}
Context: {recent interactions, open threads}
Prep: {what to know before this meeting}
## Open Threads
- {thread from yesterday, with context}
## Tasks (P0-P1)
- {task with priority}
Anti-Patterns
- Listing meetings without loading attendee context from brain
- Ignoring yesterday's unresolved threads
- Presenting tasks without priority ordering
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.
- 4d ago First seen · 62 lines · 33 tokens per session scan A b2340d2819b5
daily-task-prep is a skill published in the GitHub repository garrytan/gbrain (29,539 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 440 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…