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-gitgit 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-git)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-memory-log-git"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-log-git/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-git"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-memory-log-git.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.00017 | $0.00315 |
| Opus 5 | $0.00009 | $0.00158 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
groove-utilities-memory-log-git 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 10d 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-git
Outcome
.groove/memory/git/YYYY-MM-DD-GIT-N.md is created with a git summary for the current session. N is auto-incremented based on existing files for that date.
Acceptance Criteria
- File created at
.groove/memory/git/YYYY-MM-DD-GIT-N.mdwith correct N - Content includes commits since midnight, git status, and diff stats
- N does not collide with existing files for the same date
- File is suitable for inclusion in the same commit it describes
Constraints
- Memory path is always
.groove/memory/ - Always list existing files in
.groove/memory/git/before writing to determine correct N - N starts at 1 for the first file of the day, increments for subsequent
- Git data to include:
git log --since=midnight --onelinefor commitsgit status --shortfor current stategit diff --stat HEADfor changed files summary
- Use template at
skills/groove-utilities-memory-log-git/templates/git.mdfor file structure - If no git changes since midnight, still write the file noting no changes
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.
- 10d ago First seen · 34 lines · 17 tokens per session scan A dc27dbad4031
groove-utilities-memory-log-git is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 315 once invoked, about $0.0001 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
git-ai-search
Search and restore AI conversation context from git history.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
mulch-record-from-evidence
Turn the evidence of a finished work session — git commits, changed files, recently-touched seeds issues — into well-formed ml record invocations. Use at session close, when an agent has made changes worth preserving as mulch expertise but hasn't yet recorded them.
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.
release-prep
Orchestrates the full release preparation flow for a plugin — version sync across 7+ files, bilingual release notes creation, and commit message drafting. Use before submitting a PR. Does NOT push or create a PR; that is handled by pr-submitter.