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-mistakesgit 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-mistakes)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-mistakes"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-mistakes/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-mistakes"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-mistakes.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.00040 | $0.00782 |
| Opus 5 | $0.00020 | $0.00391 |
| Sonnet 5 | $0.00008 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
groove-utilities-memory-mistakes 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-utilities-memory-mistakes
Use $ARGUMENTS as the mistake description if provided (e.g. --list to show open incidents only).
Outcome
The workflow mistake is logged, its root cause is fixed in the relevant memory or learned file, and the lesson is graduated to .groove/memory/learned/<topic>.md. The incident is closed.
Acceptance Criteria
- Incident is recorded with root cause and fix
- Permanent fix applied to
.groove/memory/learned/<topic>.md - Incident marked resolved
Task backend
Read tasks.backend from .groove/index.md. Incidents are tracked as tasks in the configured backend. If no task backend is configured (tasks.backend: none), tell the user to run /groove-utilities-task-install first.
Incidents are stored as bugs under a shared "Groove Memory" milestone → "Mistakes" epic.
Ensure parent hierarchy
Before any operation, resolve or create the parent epic:
- Find or create the Groove Memory milestone:
beans list -t milestone --search "Groove Memory" -q— if non-empty, use first ID; otherwisebeans create "Groove Memory" -t milestone
- Find or create the Mistakes epic under that milestone:
beans list -t epic --parent <milestone-id> --search "Mistakes" -q— if non-empty, use first ID; otherwisebeans create "Mistakes" -t epic --parent <milestone-id>
--list
- Resolve
<parent-id> beans list --parent <parent-id> -t bug -s in-progress- Display as numbered list:
1. [<id>] <title> - If empty: print "No open incidents."
Log and resolve an incident
- Resolve
<parent-id> - Get description from $ARGUMENTS or ask: "What mistake did I make?"
- Ask: "Root cause — why did it happen?" (propose from context; user confirms)
- Ask: "What fix should be applied?" (propose; user confirms)
beans create "<description>" -t bug --parent <parent-id> -s in-progress- Apply the fix immediately (edit the relevant file)
- Ask: "Which learned topic? (e.g.
anti-patterns,tools)" — suggest based on root cause - Append lesson to
.groove/memory/learned/<topic>.mdunder## YYYY-MM-DDheading beans update <id> -s completed- Report: "Incident resolved → learned/.md"
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 · 67 lines · 40 tokens per session scan A bf82f5fcb23b
groove-utilities-memory-mistakes is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 782 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.