agentmods.dev

groove-admin-doctor

groove-admin-doctor is a skill for Claude Code from andreadellacorte/groove. It costs 23 tokens per session (1,387 once invoked), scanned A, original, MIT.

A health-check command for the Groove setup, including its configuration, task system, memory folders, companion tools, and editor integrations.

In plain words
What is it for?
Use it to verify the Git repository, Groove version, task backend, memory directories, companion skills, and platform links such as Cursor or Claude Code.
Why use it?
It shows which parts are working and gives a specific action for each missing or misconfigured part.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool; mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is ✓ .claude/skills/groove → ../../.agents/skills/groove.

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

Good fit Use it to verify the Git repository, Groove version, task backend, memory directories, companion skills, and platform links such as Cursor or Claude Code.

Compare 6 skills from other repositories ↓
View source ↗ andreadellacorte/groove
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/andreadellacorte/groove
agentmods
npx agentmods add skills/andreadellacorte/groove/groove-admin-doctor

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-admin-doctor

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/andreadellacorte/groove/groove-admin-doctor"><img src="https://agentmods.dev/badge/skills/andreadellacorte/groove/groove-admin-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,387 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 10 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.00023 $0.01387
Opus 5 $0.00012 $0.00694
Sonnet 5 $0.00005 $0.00277
Haiku 4.5 $0.00002 $0.00139

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

Security

Grade A, and why

groove-admin-doctor 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 11d 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-admin-doctor/SKILL.md · 103 lines

How it starts

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

groove-admin-doctor

Outcome

All groove sub-skill health checks are run and a consolidated summary is reported. User knows exactly what is working, what is misconfigured, and what action to take for any failure.

Acceptance Criteria

  • /groove-utilities-task-doctor and /groove-utilities-memory-doctor are run
  • Companion skill presence is checked directly
  • Results are shown per sub-skill with pass/fail per check
  • Overall status is shown: all healthy, or N issues found
  • Each failure includes a specific remediation action

Output format

groove doctor
─────────────────────────────────────
groove
  ✓ git repo: detected
  ✓ groove-version: 0.1.0
  ✓ installed version: 0.1.0
  ✓ up to date

task
  ✓ .groove/index.md present
  ✓ tasks.backend: beans
  ✓ beans installed (v0.x.x)
  ✓ .beans.yml present
  ✓ beans reachable

memory
  ✓ memory path exists (.groove/memory/) [hardcoded]
  ✓ memory dirs exist (.groove/memory/daily/, weekly/, monthly/, git/)

companions
  ✓ find-skills installed
  ✓ agent-browser installed
  ✓ pdf-to-markdown installed

platform symlinks
  ✓ .claude/skills/groove → ../../.agents/skills/groove
  ✗ .cursor/skills/ missing — run: /groove-admin-install

─────────────────────────────────────
1 issue found. Run the suggested commands above to fix.

Constraints

  • Run git repo check first, then version check, then /groove-utilities-task-doctor, /groove-utilities-memory-doctor, companions check in sequence
  • Git repo check:
    • Run git rev-parse --is-inside-work-tree in the current directory
    • If it succeeds: ✓ git repo: detected
    • If it fails: ✗ git repo: not a git repository — groove requires a git repo
  • Version check:
    • Read groove-version: from .groove/index.md (if absent, treat as 0.1.0)
    • Read version: from skills/groove/SKILL.md
    • If they differ: ✗ groove-version (<local>) behind installed (<installed>) — run: /groove-admin-update
  • Companions check:
    • Check ls .agents/skills/find-skills/SKILL.md — if absent: ✗ find-skills not installed — run: /groove-admin-install
    • Check ls .agents/skills/agent-browser/SKILL.md — if absent: ✗ agent-browser not installed — run: /groove-admin-install
    • Check ls .agents/skills/pdf-to-markdown/SKILL.md — if absent: ✗ pdf-to-markdown not installed — run: /groove-admin-install
  • Platform symlinks check (after companions):
    • For each groove-* directory in .agents/skills/: check that .claude/skills/<name> is a symlink pointing to ../../.agents/skills/<name>
      • If missing or not a symlink: ✗ .claude/skills/<name> not a symlink — run: /groove-admin-install
      • If symlink is broken (target doesn't exist): ✗ .claude/skills/<name> broken symlink — run: /groove-admin-install
    • Check if .cursor/skills/ directory exists:
      • If absent: ✗ .cursor/skills/ missing — run: /groove-admin-install
      • If present: check each groove symlink as above
    • All symlinks healthy: ✓ platform symlinks (.claude/, .cursor/)
  • Claude Code native hooks check (after platform symlinks):
    • Check if .claude/settings.json exists
    • If it exists: parse JSON and verify groove's hook entries are present (daily-end-reminder, git-activity-buffer, block-managed-paths, context-reprime, version-check, session-capture commands in the hooks key)
      • Each missing entry: ✗ .claude/settings.json missing groove hook <name> — run: /groove-admin-claude-hooks
    • If absent: ℹ .claude/settings.json not present — run /groove-admin-claude-hooks to install native hooks (optional)
    • All present: ✓ Claude Code native hooks (daily-end-reminder, git-activity-buffer, block-managed-paths, context-reprime, version-check, session-capture)
  • Cursor native hooks check (after Claude Code hooks):
    • Check if .cursor/ directory exists
    • If .cursor/ exists:
      • Check if .cursor/hooks.json exists
      • If it exists: parse JSON and verify groove's hook entries are present (context-reprime, daily-end-reminder, git-activity-buffer, block-managed-paths, version-check, session-capture commands in the hooks key)
        • Each missing entry: ✗ .cursor/hooks.json missing groove hook <name> — run: /groove-admin-cursor-hooks
      • If absent: ℹ .cursor/hooks.json not present — run /groove-admin-cursor-hooks to install native hooks (optional)
      • All present: ✓ Cursor native hooks (context-reprime, daily-end-reminder, git-activity-buffer, block-managed-paths, version-check, session-capture)
    • If .cursor/ absent: skip silently (Cursor not in use)
  • Collect all results before printing — do not interleave output with check progress
  • Each ✗ item must include a concrete remediation command on the same line
  • Exit with a clear "all healthy" message if no issues found
  • Do not attempt to auto-fix issues — report only

Read the full file on GitHub · 103 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. 11d ago First seen · 103 lines · 23 tokens per session scan A 8da7f49ae866

Subscribe to this mod's changes

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

Debugging
Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens