groove-utilities-memory-promises

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

A tracker for tasks or decisions that were postponed during a work session.

In plain words
What is it for?
Use it to record a deferred item, list open promises, or mark a numbered promise as resolved.
Why use it?
It prevents “we’ll come back to that” items from being forgotten and lets you review or close them later.

Skill for Claude Code

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

Good fit Use it to record a deferred item, list open promises, or mark a numbered promise as resolved.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/andreadellacorte/groove/groove-utilities-memory-promises
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-promises
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-promises

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-promises"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-promises.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 855 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 4 Oct 2026
  • Snyk pass 4 Oct 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.00042 $0.00855
Opus 5.5 $0.00017 $0.00342
Sonnet 5.5 $0.00008 $0.00171
Haiku 4.5 $0.00004 $0.00085

Measured 2mo ago against content hash 1838ef5d8747, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

skills/groove-utilities-memory-promises/SKILL.md · 75 lines

How it starts

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

groove-utilities-memory-promises

Use $ARGUMENTS as the promise text if provided, or a flag:

  • --list: show all open promises
  • --resolve <N>: mark promise N as resolved

Outcome

Deferred items from a session are captured before they are forgotten, or existing open promises are reviewed and resolved.

Acceptance Criteria

  • New promise captured with date and optional context
  • --list shows all open promises clearly numbered
  • --resolve N marks promise N as resolved

Task backend

Read tasks.backend from .groove/index.md. Promises 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.

Promises are stored as tasks under a shared "Groove Memory" milestone → "Promises" epic hierarchy. This keeps them organised and out of the main work task list.

Ensure parent hierarchy

Before any operation, resolve or create the parent epic:

  1. Find or create the Groove Memory milestone:
    • beans list -t milestone --search "Groove Memory" -q — if output is non-empty, use the first ID; otherwise beans create "Groove Memory" -t milestone and capture the new ID
  2. Find or create the Promises epic under that milestone:
    • beans list -t epic --parent <milestone-id> --search "Promises" -q — if non-empty, use first ID; otherwise beans create "Promises" -t epic --parent <milestone-id> and capture the new ID

Use the Promises epic ID as <parent-id> for all promise tasks.

--list

  1. Resolve <parent-id> (see above)
  2. beans list --parent <parent-id> -s todo -t task
  3. Display as numbered list: 1. [<id>] <title> — position number for --resolve N, beans ID in brackets
  4. If empty: print "No open promises."

--resolve <N>

  1. Resolve <parent-id>; run beans list --parent <parent-id> -s todo -t task
  2. Find the Nth item; if not found: print "No open promise #N" and exit
  3. beans update <id> -s completed
  4. Confirm: "Promise #N resolved."

Read the full file on GitHub · 75 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. 2mo ago First seen · 75 lines · 42 tokens per session scan A 1838ef5d8747

Subscribe to this mod's changes

groove-utilities-memory-promises is a skill published in the GitHub repository andreadellacorte/groove (6 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 855 once invoked, about $0.0002 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.

Related

groove-utilities-memory-promises compared with skills from other repositories

groove-utilities-memory-promises next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
groove-utilities-memory-promisesandreadellacorte/grooveSkill63mo agoMITA42Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code