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-configgit 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-config)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-admin-config"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-admin-config/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-admin-config"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-admin-config.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.00022 | $0.01213 |
| Opus 5 | $0.00011 | $0.00607 |
| Sonnet 5 | $0.00004 | $0.00243 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
groove-admin-config 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 9d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-admin-config
Outcome
.groove/index.md is created or updated with values confirmed by the user. The git strategy is applied immediately. User is ready to run /groove-admin-install.
Acceptance Criteria
.groove/index.mdexists with all config keys populated- Each key was either confirmed by the user or accepted as default
- Git strategy is applied (
.groove/.gitignorewritten) before exiting - User is shown a summary of the final config and told to run
/groove-admin-install
Steps
If --defaults is passed: skip all prompts, apply all defaults, and proceed directly to writing the config (step 1 of "After all keys are confirmed"). Report the defaults being applied.
Otherwise, walk the user through each config key in order. For each key: show the current value (or default if new), explain what it does, and ask to confirm or change.
Keys and defaults
| Key | Default | Options | Question to ask |
|---|---|---|---|
tasks.storage |
beans |
beans | linear | github | none |
"Which task backend? beans tracks tasks as markdown files in your repo." |
tasks.list_limit |
15 |
positive integer | "Max tasks shown by task-list? (default: 15)" |
tasks.analyse_limit |
30 |
positive integer | "Max tasks shown by task-analyse? (default: 30)" |
memory.review_days |
5 |
positive integer | "How many recent business days to review at daily start? (default: 5)" |
git.memory |
ignore-all |
ignore-all | hybrid | commit-all |
"Git strategy for memory logs? ignore-all keeps them local, hybrid commits logs but ignores sessions, commit-all commits everything." |
git.tasks |
ignore-all |
ignore-all | commit-all |
"Git strategy for task files (.groove/tasks/)? ignore-all keeps them local, commit-all tracks them in git." |
git.hooks |
commit-all |
ignore-all | commit-all |
"Git strategy for hooks (.groove/hooks/)? commit-all shares hooks with the team, ignore-all keeps them local." |
groovebook |
andreadellacorte/groovebook |
<owner>/<repo> or blank |
"Groovebook repo for sharing learnings? Default: andreadellacorte/groovebook. Leave blank to disable." |
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.
- 9d ago First seen · 84 lines · 22 tokens per session scan A 769e3f9291c1
groove-admin-config is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,213 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…