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-cursor-hooksgit 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-cursor-hooks)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-admin-cursor-hooks"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-admin-cursor-hooks/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-cursor-hooks"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-admin-cursor-hooks.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.00047 | $0.02332 |
| Opus 5.5 | $0.00019 | $0.00933 |
| Sonnet 5.5 | $0.00009 | $0.00466 |
| Haiku 4.5 | $0.00005 | $0.00233 |
Grade A, and why
groove-admin-cursor-hooks 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.
How it starts
The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-admin-cursor-hooks
Install groove's Cursor native hooks. These run outside the model — deterministic, unconditional — and complement groove's advisory markdown hooks (.groove/hooks/start.md, end.md).
Use --disable <hook> to remove a specific hook. Use --list to show current status.
Outcome
Selected hooks are registered in .cursor/hooks.json and shell scripts are written to .groove/hooks/cursor/. Hooks fire automatically on Cursor lifecycle events without any model involvement.
Available hooks
| Name | Event | Matcher | What it does |
|---|---|---|---|
context-reprime |
sessionStart |
— | Runs the prime script with --json — ensures full workflow context is loaded after every session start and compaction |
daily-end-reminder |
stop |
— | If hour is 16–21 local time and .groove/index.md exists, prints a reminder to run /groove-daily-end |
git-activity-buffer |
postToolUse |
Shell |
If the command contains git commit, appends a timestamped line to .groove/.cache/git-activity-buffer.txt |
block-managed-paths |
preToolUse |
Write |
If file_path starts with .agents/skills/groove or skills/groove, exits with code 2 to block the write with an explanatory message |
version-check |
postToolUse |
— | Checks for a new groove version once per hour; calls groove-utilities-check |
session-capture |
stop |
— | If there is git activity this session (commits since midnight, working changes, or buffered commits), stages a capture draft to .groove/.cache/pending-capture.md for next-session review. Silent. |
Steps
--list
Read .cursor/hooks.json if it exists. Report which groove hooks are registered and which scripts exist in .groove/hooks/cursor/. Exit.
--disable <hook>
Remove the named hook's entry from .cursor/hooks.json (leave the script in place). Report removed / not found. Exit.
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.
- 2mo ago First seen · 222 lines · 47 tokens per session scan A 9f46f8d3cf06
groove-admin-cursor-hooks is a skill published in the GitHub repository andreadellacorte/groove (6 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 2,332 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.
groove-admin-cursor-hooks compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| groove-admin-cursor-hooksandreadellacorte/groove | Skill | 6 | 3mo ago | MIT | A | 47 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |