groove-utilities-memory-graduate

groove-utilities-memory-graduate is a skill for Claude Code from andreadellacorte/groove. It costs 41 tokens per session (716 once invoked), scanned A, original, MIT.

A tool that promotes a stable lesson from groove's learned-memory files into AGENTS.md, the project-wide instructions file read by coding agents.

In plain words
What is it for?
Use it to select a learned insight, confirm its wording, and add it as a permanent project constraint.
Why use it?
It makes an important lesson visible in every future session instead of leaving it buried in project memory.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool; mentions AGENTS.md.

Good fit Use it to select a learned insight, confirm its wording, and add it as a permanent project constraint.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/andreadellacorte/groove/groove-utilities-memory-graduate
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 andreadellacorte/groove --skill groove-utilities-memory-graduate
Clone the repo
git clone --depth 1 https://github.com/andreadellacorte/groove

Made for: Claude Code.

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 groove-utilities-memory-graduate

README.md
[![agentmods](https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-graduate/github.svg)](https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-graduate)
Your own site
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-graduate"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-graduate/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 groove-utilities-memory-graduate

Your own site · 80×15
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-graduate"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-graduate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 716 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
  • Socket pass 18 Mar 2026
  • Snyk pass 10 Mar 2026
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.00041 $0.00716
Opus 5 $0.00020 $0.00358
Sonnet 5 $0.00008 $0.00143
Haiku 4.5 $0.00004 $0.00072

Measured 12d ago against content hash 11826bec51ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

groove-utilities-memory-graduate 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.

skills/groove-utilities-memory-graduate/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

groove-utilities-memory-graduate

Promote a stable workflow insight from .groove/memory/learned/ into AGENTS.md as a permanent constraint — visible to every agent session without needing to run prime.

Use $ARGUMENTS as the topic or insight text if provided.

Outcome

The lesson is appended to a <!-- groove:learned:start --> / <!-- groove:learned:end --> section in AGENTS.md, making it permanently visible to all future sessions.

Acceptance Criteria

  • Insight is appended to the ## Graduated Learnings section in AGENTS.md
  • Section is created if it does not exist
  • User confirms the exact text before writing
  • Source learned/<topic>.md entry is marked as graduated (not deleted)

Steps

  1. Memory path is always .groove/memory/
  2. If $ARGUMENTS names a topic, read .groove/memory/learned/<topic>.md and show its entries. Otherwise, list all *.md files in .groove/memory/learned/ and ask which topic to graduate from.
  3. Show the file contents; ask: "Which entry should be graduated? (paste or describe it)"
  4. Show the exact text that will be written to AGENTS.md; ask: "Confirm? (yes / edit / skip)"
  5. If confirmed: write to AGENTS.md (see section management below)
  6. Mark the entry in the learned file by appending [graduated YYYY-MM-DD] inline after the bullet
  7. Report: "Lesson graduated to AGENTS.md → ## Graduated Learnings"

Section management in AGENTS.md

Look for a <!-- groove:learned:start --> / <!-- groove:learned:end --> block:

  • If the block exists: append the new insight as a bullet under ## Graduated Learnings inside the block
  • If the block does not exist: append the following to the end of AGENTS.md:
<!-- groove:learned:start -->
## Graduated Learnings

Stable workflow insights promoted from `.groove/memory/learned/`. These apply to every session.

- <insight text>
<!-- groove:learned:end -->

Each entry is a single bullet: - <insight text> *(from learned/<topic>.md, graduated YYYY-MM-DD)*

Constraints

Read the full file on GitHub · 64 lines

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. 12d ago First seen · 64 lines · 41 tokens per session scan A 11826bec51ad

Subscribe to this mod's changes

groove-utilities-memory-graduate is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 716 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.

Related

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.

garrytan/gbrain · 52 tokens

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

mem0ai/mem0 · 273 tokens

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…

danielmiessler/LifeOS · 196 tokens

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.

opensquilla/opensquilla · 44 tokens

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…

shiwenwen/hope-agent · 115 tokens

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.

GanyuanRan/Aegis · 45 tokens