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-task-installgit 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-task-install)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-utilities-task-install"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-task-install/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-task-install"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-utilities-task-install.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
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.00014 | $0.00700 |
| Opus 5 | $0.00007 | $0.00350 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
groove-utilities-task-install 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-utilities-task-install
Outcome
The configured task backend is installed and verified reachable. User is informed of what was installed and how to use it.
Acceptance Criteria
- Backend CLI is available in PATH after install
- User is shown a confirmation with the installed version or a reachability check
- No-op if
tasks.storage: none
Constraints
- Read
tasks.storagefrom.groove/index.mdto determine backend (if the key is still namedtasks.backendfrom an older config, treat it as the storage value). If the key is missing or invalid, you may pause and useAskUserQuestionso the user can choose a backend (beans,linear,github, ornone); then ensure.groove/index.mdis updated accordingly (via/groove-admin-configor an equivalent edit) before continuing. - If
tasks.storage: none, print friendly no-op message and exit - Installation source of truth: Do not embed OS-specific install commands in this skill. You must follow the official installation instructions from the upstream project for the user’s OS (read that page and run what it specifies). Link only:
beans: hmans/beans — Installation sectionlinear: schpet/linear-cli — install section (third-party CLI; not Linear’s hosted docs)github: GitHub CLI
- After the CLI is on PATH per those instructions, run a reachability check (
beans version,linear --version/linear --help, orgh version/gh auth statusas appropriate) - If the CLI is already installed before you start, report current version and skip fetching install instructions
- If
tasks.storage: beansand.beans.ymldoes not exist at git root:- Run
beans initto initialise the task store and generate.beans.ymlwith beans defaults - Derive
[PROJECT_PREFIX]from the git repo name (last path component ofgit remote get-url origin, stripped of.git, uppercased, non-alphanumeric stripped) — e.g.groove→GRV; fall back to the directory name if no remote - Update the
prefix:field in the generated.beans.ymlto the derived prefix (e.g.GRV-) - Set
path:in.beans.ymlto.groove/tasksso the task store lives under groove (aligned withgit.tasksand.groove/.gitignore). Create.groove/tasksif it does not exist. If the default.beansdirectory was created and is non-empty, move its contents into.groove/tasksand remove the empty.beansdirectory. - Report the path written and the prefix used
- Run
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 · 38 lines · 14 tokens per session scan A f61ae943f9f6
groove-utilities-task-install is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 700 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.