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-utilities-memory-log-weeklygit 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-utilities-memory-log-weekly)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-log-weekly"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-log-weekly/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-utilities-memory-log-weekly"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-log-weekly.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.00019 | $0.00296 |
| Opus 5.5 | $0.00008 | $0.00118 |
| Sonnet 5.5 | $0.00004 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
groove-utilities-memory-log-weekly 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 2mo 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
groove-utilities-memory-log-weekly
Outcome
.groove/memory/weekly/YYYY-Www.md is created or updated with a roll-up of the week's daily files. Sections cover themes, key outcomes, and learnings — no raw detail duplication.
Acceptance Criteria
- File exists at
.groove/memory/weekly/YYYY-Www.md(ISO week format, e.g.2026-W09) - Themes section identifies recurring topics from daily entries
- Key outcomes section lists significant completions from the week
- Learnings section synthesises patterns and insights across the week
- Content is rolled up from daily files — not duplicated raw detail
Constraints
- Memory path is always
.groove/memory/ - Only run on the last weekday of the week, or when user explicitly requests
- Roll up from that week's daily files in
.groove/memory/daily/ - If no daily files exist for the week, note that and exit gracefully
- Use template at
skills/groove-utilities-memory-log-weekly/templates/weekly.mdfor file structure - If file already exists, update rather than overwrite
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.
- 2mo ago First seen · 32 lines · 19 tokens per session scan A e62699d0bbda
groove-utilities-memory-log-weekly is a skill published in the GitHub repository andreadellacorte/groove (6 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 296 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-31.
groove-utilities-memory-log-weekly compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| groove-utilities-memory-log-weeklyandreadellacorte/groove | Skill | 6 | 3mo ago | MIT | A | 19 | Claude Code |
| knowledge-ingestopenclaw/openclaw | Skill | 394k | today | MIT | A | 80 | Claude Code, Codex |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 69k | today | Apache-2.0 | A | 217 | Claude Code, Codex |
| forgetasgeirtj/system_prompts_leaks | Skill | 71k | today | CC0-1.0 | A | 0 | Claude Code, Codex |
| Cortexdanielmiessler/LifeOS | Skill | 20k | yesterday | MIT | A | 184 | Claude Code |
| memoryopensquilla/opensquilla | Skill | 7.1k | 6d ago | Apache-2.0 | A | 44 | Claude Code, Codex |
| ha-data-storesshiwenwen/hope-agent | Skill | 1.9k | today | MIT | A | 115 | Claude Code, Codex |