agentmods.dev

groove-groovebook-publish

groove-groovebook-publish is a skill for Claude Code from andreadellacorte/groove. It costs 38 tokens per session (1,008 once invoked), scanned A, original, MIT.

A publisher that shares a reusable workflow lesson as a pull request on GitHub. A pull request is a proposed change that others can review before it is added.

In plain words
What is it for?
Use it after capturing a lesson to submit a Markdown learning file to a configured shared groovebook repository.
Why use it?
It removes the manual work of cleaning project-specific details from a lesson and preparing it for community review.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

not rated 5repo 1mo ago A scan Socket: passSnyk: pass 38 tokens original MIT

Good fit Use it after capturing a lesson to submit a Markdown learning file to a configured shared groovebook repository.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/andreadellacorte/groove/groove-groovebook-publish
View source ↗ andreadellacorte/groove
Install

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.

Any agent
npx skills add andreadellacorte/groove --skill groove-groovebook-publish
Clone the repo
git clone --depth 1 https://github.com/andreadellacorte/groove

Made for: Claude Code.

Wrote 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.

agentmods badge for groove-groovebook-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-publish/github.svg)](https://agentmods.dev/skills/andreadellacorte/groove/groove-groovebook-publish)
Your own site
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-groovebook-publish"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-publish/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.

agentmods 80×15 button for groove-groovebook-publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-groovebook-publish"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-groovebook-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,008 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 18 Mar 2026
  • Snyk pass 8 Mar 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01008
Opus 5 $0.00019 $0.00504
Sonnet 5 $0.00008 $0.00202
Haiku 4.5 $0.00004 $0.00101

Measured 12d ago against content hash 9812e9d5c501, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

groove-groovebook-publish 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.

skills/groove-groovebook-publish/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

groove-groovebook-publish

Use $ARGUMENTS as the learning text if provided.

Outcome

A learning from the current project is published to the configured groovebook repo as a pull request, stripped of any project-specific context, ready for community review.

Acceptance Criteria

  • Learning is published as a PR to <groovebook> repo
  • PR uses the groovebook PR template format (Summary, Context, Learning, Groove skill area)
  • File is written at learned/<topic>/<YYYY-MM-DD>-<slug>.md in the groovebook repo
  • PR URL is printed to the user

Steps

  1. Read groovebook: from .groove/index.md; if absent, exit with: groovebook is not configured. Add 'groovebook: <owner>/<repo>' to .groove/index.md to enable.

  2. Check gh auth status; if not authenticated, exit with: Not authenticated with GitHub. Run: gh auth login

  3. Verify the groovebook repo is accessible: gh repo view <groovebook>; if it fails, exit with a clear message.

  4. Get the learning text:

    • If $ARGUMENTS is provided, use it as a starting point
    • Otherwise: ask "What's the learning you'd like to publish? (paste it or describe briefly)"
    • Ask for a one-sentence summary (used as PR title and filename slug)

  5. Show a preview of the learning text and ask: Does this contain any repo-specific context to redact? (file paths, internal names, product names)

    • If yes: help the user redact it — replace specific names with generic descriptions
    • If no: proceed

  6. Ask for topic (e.g. patterns, tools, anti-patterns, workflow) and skill area (e.g. compound, plan, review, daily)

  7. Generate slug: lowercase the summary, replace spaces with hyphens, strip special characters, truncate to 40 chars. Construct:

    • Branch name: learning/<YYYY-MM-DD>-<slug>
    • File path: learned/<topic>/<YYYY-MM-DD>-<slug>.md

  8. Fork the groovebook repo if not already forked: gh repo fork <groovebook> --clone=false

    • If fork already exists, skip silently

  9. Create the branch and file:

    • gh api repos/<user-fork>/git/refs to check if branch exists; if so, append a short unique suffix
    • Write the file content (see format below) and commit via gh api
    • Or: use git operations against the fork URL if gh api approach is too complex — prefer the simpler path

Read the full file on GitHub · 119 lines

Changes

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.

  1. 12d ago First seen · 119 lines · 38 tokens per session scan A 9812e9d5c501

Subscribe to this mod's changes

groove-groovebook-publish is a skill published in the GitHub repository andreadellacorte/groove (5 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,008 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.

Git and workflow
Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens