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-admin-helpgit 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-admin-help)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-admin-help"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-admin-help.svg" alt="Measured on agentmods" 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.00016 | $0.01272 |
| Opus 5 | $0.00008 | $0.00636 |
| Sonnet 5 | $0.00003 | $0.00254 |
| Haiku 4.5 | $0.00002 | $0.00127 |
Grade A, and why
groove-admin-help 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 8d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-admin-help
Display a structured overview of all groove skills and their commands.
Output
Print the following, substituting live config values from .groove/index.md where shown:
groove — compound engineering workflow
/groove /groove-admin-help /groove-utilities-prime /groove-admin-install /groove-admin-config /groove-admin-update /groove-utilities-check /groove-utilities-stats /groove-admin-doctor
Daily
| Skill | Purpose |
|---|---|
/groove-daily-start |
Start the workday |
/groove-daily-end |
End the workday |
Work
| Skill | Purpose |
|---|---|
/groove-work-brainstorm |
Clarify scope through dialogue |
/groove-work-plan |
Write implementation plan |
/groove-work-exec |
Execute the plan |
/groove-work-review |
Evaluate output |
/groove-work-compound |
Capture lessons |
/groove-work-spec [topic] |
Create outcome spec (what to build) |
/groove-work-doc [topic] |
Create reference doc (how it works) |
/groove-work-audit |
Review branch for blindspots |
Utilities — Tasks
| Skill | Purpose |
|---|---|
/groove-utilities-task-list |
List active tasks |
/groove-utilities-task-create |
Create a task |
/groove-utilities-task-update |
Update a task |
/groove-utilities-task-archive |
Archive a task |
/groove-utilities-task-analyse |
Analyse task status |
/groove-utilities-task-install |
Set up task backend |
/groove-utilities-task-config |
Configure task backend |
/groove-utilities-task-doctor |
Check task backend health |
Utilities — Memory
| Skill | Purpose |
|---|---|
/groove-utilities-memory-log-daily |
Write daily log entry |
/groove-utilities-memory-log-weekly |
Roll up weekly log |
/groove-utilities-memory-log-monthly |
Roll up monthly log |
/groove-utilities-memory-log-git |
Record git activity |
/groove-utilities-memory-install |
Set up memory backend |
/groove-utilities-memory-doctor |
Check memory backend health |
/groove-utilities-memory-mistakes |
Log and resolve a workflow mistake |
/groove-utilities-memory-promises |
Capture or resolve a deferred item |
/groove-utilities-memory-retrospective [week|month|all] |
Analyse ratings, mistakes, learnings |
/groove-utilities-memory-graduate [topic] |
Promote a stable lesson to AGENTS.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.
- 8d ago First seen · 126 lines · 16 tokens per session scan A 5cfc68fd76bd
groove-admin-help is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,272 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…