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-retrospectivegit 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-retrospective)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-retrospective"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-retrospective/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-retrospective"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-retrospective.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.00033 | $0.00943 |
| Opus 5 | $0.00016 | $0.00472 |
| Sonnet 5 | $0.00007 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
groove-utilities-memory-retrospective 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 12d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-utilities-memory-retrospective
Use $ARGUMENTS to specify period: week (default), month, or all.
Outcome
A period retrospective is output to the conversation: session rating trend, recurring mistake patterns, top learnings captured, and a short workflow health summary. No files are written.
Acceptance Criteria
- Session ratings trend shown (if
learned/signals.mdhas data) - Mistake patterns summarised (from resolved incidents in task backend)
- Top learnings listed by topic (from
learned/*.mddated entries) - Workflow health summary: one sentence on overall trend
- All output goes to conversation only
Steps
-
Memory path is always
.groove/memory/ -
Determine date range from $ARGUMENTS:
week: last 7 days (today - 7)month: last 30 daysall: all available data- Default if absent:
week
-
Session ratings — read
.groove/memory/learned/signals.mdif it exists:- Parse table rows matching the date range:
| YYYY-MM-DD | N/5 | context | - Compute: count, average rating, trend (last 3 vs first 3 if enough data)
- If no data: note "No session ratings recorded yet"
- Parse table rows matching the date range:
-
Mistakes — query the task backend for resolved incidents under "Groove Memory" → "Mistakes":
beans list --parent <mistakes-epic-id> -t bug -s completedfor resolved;-s in-progressfor open- Group by title keywords to identify recurring patterns
- Count total resolved vs open incidents
- If no task backend or no data: note "No incidents recorded yet"
-
Learnings — glob
.groove/memory/learned/*.md(excludesignals.md):- For each file: read and collect dated entries (
## YYYY-MM-DDheadings) within the date range - Group by topic (filename stem)
- Count entries per topic; show the most recent bullet per topic as a sample
- If no files: note "No learnings captured yet"
- For each file: read and collect dated entries (
-
Git activity — run
git log --oneline --since="<start-date>"to count commits in the period as a proxy for work volume
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.
- 12d ago First seen · 95 lines · 33 tokens per session scan A e07388cee44e
groove-utilities-memory-retrospective is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 943 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.