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 andreadellacorte/groove --skill groove-daily-startgit clone --depth 1 https://github.com/andreadellacorte/grooveWrote 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/andreadellacorte/groove/groove-daily-start)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-daily-start"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-daily-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/andreadellacorte/groove/groove-daily-start"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-daily-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00031 | $0.00749 |
| Opus 5 | $0.00015 | $0.00375 |
| Sonnet 5 | $0.00006 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
groove-daily-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 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-daily-start
Outcome
The workday is prepared: recent days are reviewed, today's daily memory file is created, tasks are consolidated and presented, and the user knows what to work on.
Acceptance Criteria
- Yesterday's daily memory file is reviewed (summary shown; warn if missing or no end section)
- Today's daily memory file is created with a start-of-day structure (if it does not already exist)
- Task list is loaded and presented (grouped by status)
- User has a clear picture of the day's agenda before starting work
Constraints
- Read
.groove/index.mdfortasks.backendandmemory.review_daysconfig - Memory path is always
.groove/memory/ - Call
/groove-utilities-task-analyseto get current task state - Review recent days: If
.groove/memory/daily/is empty (no files exist), skip this step entirely and note "Fresh install — no prior logs." Otherwise, identify the lastmemory.review_daysbusiness days (Mon–Fri) counting back from yesterday (skip Saturday and Sunday). For each date:- Check
.groove/memory/daily/YYYY-MM-DD.md:✓ YYYY-MM-DD — start + end loggedif both start-of-day and end sections exist~ YYYY-MM-DD — start only, no end loggedif only start section present✗ YYYY-MM-DD — missingif file does not exist- Show a one-line context from the file if present (e.g. first bullet from "Done today" or plan intent)
- Show git activity: run
git log --oneline --after="YYYY-MM-DD 00:00" --before="YYYY-MM-DD 23:59:59"— display commit count and first few titles; skip silently if not in a git repo or no commits - Do NOT block start if files are missing or incomplete — just report
- Check
- Create new day memory: Create today's file at
.groove/memory/daily/YYYY-MM-DD.mdusing the template atskills/groove-daily-start/templates/daily-start.md. If the file already exists, skip (idempotent). Create.groove/memory/daily/if missing. - After the recent-days review, check for open promises via
/groove-utilities-memory-promises --list:- If open promises: show inline note:
→ N open promise(s) — run /groove-utilities-memory-promises --list to review - If none: skip silently
- If open promises: show inline note:
- After the recent-days review, check for open mistake incidents via
/groove-utilities-memory-mistakes --list:- If open incidents: show inline warning:
⚠ N open incident(s) — resolve at next /groove-work-compound - If none: skip silently
- If open incidents: show inline warning:
- Do NOT modify tasks during start
- Present task list in a scannable format before the user begins
- After all standard steps: check if
.groove/hooks/start.mdexists- If it exists: read the
## Actionssection and execute each item in order; report completion per item - If it does not exist: skip silently
- If it exists: read the
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 48 lines · 31 tokens per session scan A c1ea774aebc4
groove-daily-start is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 749 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-31.
Other skills, from other repositories
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…
Migrate
Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
email-assistant
Read, search, draft, and send emails via Himalaya CLI or Python IMAP/SMTP. Requires email account configuration.
calendar
Manage calendar events via CalDAV (Google/iCloud/Nextcloud) or local ICS files. View, create, and query events.