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-groovebook-reviewgit 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-groovebook-review)<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-groovebook-review"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-review/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-groovebook-review"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-review.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.00031 | $0.00607 |
| Opus 5 | $0.00015 | $0.00303 |
| Sonnet 5 | $0.00006 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
groove-groovebook-review 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 12d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
groove-groovebook-review
Outcome
Open learning PRs in the groovebook repo are listed; the user reviews one and submits a reaction (approve, comment, or request changes).
Acceptance Criteria
- Open PRs are listed with title, author, and date
- User selects a PR to review; diff and body are shown
- User submits a reaction via
gh pr review
Steps
-
Read
groovebook:from.groove/index.md; if absent, exit with:groovebook is not configured. Add 'groovebook: <owner>/<repo>' to .groove/index.md to enable. -
Check
gh auth status; if not authenticated, exit with:Not authenticated with GitHub. Run: gh auth login -
List open PRs:
gh pr list --repo <groovebook> --state open --json number,title,author,createdAt- If none open: print "No open learning PRs in ." and exit
- Display as a numbered list:
N. #<number> — <title> (by <author>, <date>)
-
Ask: "Which PR would you like to review? (enter number or PR #)"
-
Show the PR:
gh pr view <number> --repo <groovebook>— show bodygh pr diff <number> --repo <groovebook>— show diff
-
Ask: "Your reaction? (approve / comment / request-changes)"
- If
comment: ask for the comment text - If
request-changes: ask for the request text - If
approve: confirm intent
- If
-
Submit:
gh pr review <number> --repo <groovebook> --<approve|comment|request-changes> --body "<text>"For approve:
gh pr review <number> --repo <groovebook> --approve -
Confirm submission and print the PR URL.
-
Optional follow-up: ask "Does this learning suggest a change to a groove skill? If so, consider opening a companion PR to the groove repo referencing this groovebook PR."
Constraints
- Read-only until step 7 — do not modify any local files
- If
gh pr diffoutput is very large (>200 lines), show only the first 50 lines and note it's truncated - The
approvereaction should always ask for confirmation before submitting — approvals are harder to undo than comments
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.
- 12d ago First seen · 63 lines · 31 tokens per session scan A fb448b33d97a
groove-groovebook-review is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 607 once invoked, about $0.0002 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.