daily-task-prep

daily-task-prep is a skill for Claude Code from garrytan/gbrain. It costs 33 tokens per session (585 once invoked), scanned A, original, MIT.

A morning preparation workflow that combines today's calendar, meeting context, unresolved threads from yesterday, and active tasks. It turns that information into an actionable briefing before the day begins.

In plain words
What is it for?
Use it to prepare context cards for meetings, identify unanswered items, review high-priority tasks, and decide what to do before each appointment.
Why use it?
It reduces the time spent gathering background before meetings and makes unfinished conversations and urgent work easier to spot.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: built for gbrain.

Part of the gbrain-daily plugin — 15 skills shipped together

Good fit Use it to prepare context cards for meetings, identify unanswered items, review high-priority tasks, and decide what to do before each appointment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/garrytan/gbrain/daily-task-prep
About the project

GBrain is a memory and retrieval layer for AI agents that searches, connects, and synthesizes information from stored sources. It is used to give coding agents and autonomous agents access to knowledge beyond their current code, including shared company information with access controls. The catalogue add-ons help agents operate GBrain and connect it to agent workflows.

garrytan/gbrain · 31,098 stars · on GitHub

Install

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.

Any agent
npx skills add garrytan/gbrain --skill daily-task-prep
Clone the repo
git clone --depth 1 https://github.com/garrytan/gbrain

Made for: Claude Code.

Or install gbrain-daily, the plugin that ships this one along with the rest of its 15 skills.

Wrote 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.

agentmods badge for daily-task-prep

README.md
[![agentmods](https://agentmods.dev/badge/skills/garrytan/gbrain/daily-task-prep/github.svg)](https://agentmods.dev/skills/garrytan/gbrain/daily-task-prep)
Your own site
<a href="https://agentmods.dev/skills/garrytan/gbrain/daily-task-prep"><img src="https://agentmods.dev/badge/skills/garrytan/gbrain/daily-task-prep/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.

agentmods 80×15 button for daily-task-prep

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 585 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Snyk pass 7 Sept 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 34
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00585
Opus 5.5 $0.00013 $0.00234
Sonnet 5.5 $0.00007 $0.00117
Haiku 4.5 $0.00003 $0.00059

Measured 15d ago against content hash 14bbf381ee9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 15d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

plugin-variants/gbrain-daily/skills/daily-task-prep/SKILL.md · 70 lines

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

  1. Load calendar. Check today's meetings. For each: load attendee brain pages, recent timeline, open threads.
  2. Check yesterday's threads. When google sources exist, gbrain waiting --json is 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; see skills/google-loops/SKILL.md). Otherwise, search brain for yesterday's timeline entries. Flag anything unresolved.
  3. Review active tasks. Load ops/tasks from brain. Surface P0 and P1 items.
  4. 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}

When it fails

Follow the agent operator protocol for any gbrain error code, exit code, [AGENT] block or notice block. Specific to this skill:

  • gbrain waiting refuses on stale data: run (or ask the user to run) the sync it names, then retry; do not prep from stale mail.
  • Meeting-context searches return nothing with a degraded notice: say the brain is searching keywords only right now, instead of "no prior context".

Anti-Patterns

  • Listing meetings without loading attendee context from brain
  • Ignoring yesterday's unresolved threads
  • Presenting tasks without priority ordering
Changes

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.

  1. 15d ago Changed · -9 lines 14bbf381ee9e
  2. 16d ago Changed 498df45338ba
  3. 17d ago Changed · +1 lines 9780d9d51256
  4. 18d ago Changed 321603e53190
  5. 19d ago Changed · +16 lines c308a2ae2d37
  6. 1mo ago First seen · 62 lines · 33 tokens per session scan A b2340d2819b5

Subscribe to this mod's changes

daily-task-prep is a skill published in the GitHub repository garrytan/gbrain (31,098 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 585 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-30.

Related

Other skills, from other repositories

gsd-ns-manage

Invoke this Pi skill with /skill:gsd-ns-manage.

open-gsd/gsd-core · 16 tokens

feature-prioritisation

Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…

mohitagw15856/pm-claude-skills · 103 tokens

to-spec

A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.

vinvcn/mattpocock-skills-zh-CN · 29 tokens

design-handoff-brief

Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…

mohitagw15856/pm-claude-skills · 83 tokens

triage-inbox

Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…

pedrohcgs/claude-code-my-workflow · 132 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens