check-contributors

check-contributors is a command for Claude Code from alinaqi/maggy. It costs 0 tokens per session (1,450 once invoked), scanned A, original, MIT.

A project command that identifies whether a code project is being developed by one person or a team and shows current contributors and assignments. It uses project files and Git history, where Git records changes to code over time.

In plain words
What is it for?
Use it to inspect contributors, active work, claimed tasks, recent activity, and possible conversion from a solo project to a team-managed project.
Why use it?
It gives a quick view of who is working on what and whether team coordination is already set up.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: reads .claude/ paths; mentions CLAUDE.md.

Good fit Use it to inspect contributors, active work, claimed tasks, recent activity, and possible conversion from a solo project to a team-managed project.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/alinaqi/maggy/check-contributors
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.

Clone the repo
git clone --depth 1 https://github.com/alinaqi/maggy

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 check-contributors

README.md
[![agentmods](https://agentmods.dev/badge/commands/alinaqi/maggy/check-contributors/github.svg)](https://agentmods.dev/commands/alinaqi/maggy/check-contributors)
Your own site
<a href="https://agentmods.dev/commands/alinaqi/maggy/check-contributors"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/check-contributors/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 check-contributors

Your own site · 80×15
<a href="https://agentmods.dev/commands/alinaqi/maggy/check-contributors"><img src="https://agentmods.dev/badge/commands/alinaqi/maggy/check-contributors.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,450 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.
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.00000 $0.01450
Opus 5 $0.00000 $0.00725
Sonnet 5 $0.00000 $0.00290
Haiku 4.5 $0.00000 $0.00145

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

Security

Grade A, and why

check-contributors 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.

commands/check-contributors.md · 289 lines

How it starts

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

Check Contributors

Checks who's working on the project and optionally converts to a multi-person project with team state management.


What This Command Does

  1. Detect current state - Is this a solo or team project?
  2. Show active contributors - Who's working on what right now?
  3. Offer conversion - Convert solo → team project if needed

Phase 1: Detect Project Type

Check for team structure:

# Check if team coordination exists
ls _project_specs/team/state.md 2>/dev/null
ls _project_specs/team/contributors.md 2>/dev/null

# Check git contributors
git shortlog -sn --all 2>/dev/null | head -10

# Check recent activity
git log --oneline --since="7 days ago" --format="%an" | sort | uniq -c | sort -rn

If Team Structure Exists

Report current state:

📊 Team Project Detected

Contributors:
┌──────────┬────────────────┬──────────┐
│ Handle   │ Focus Area     │ Status   │
├──────────┼────────────────┼──────────┤
│ @alice   │ Backend, Auth  │ 🟢 Active │
│ @bob     │ Frontend       │ 🟡 Paused │
└──────────┴────────────────┴──────────┘

Active Sessions:
• @alice working on TODO-042 (src/auth/*)
• No conflicts detected

Claimed Todos:
• TODO-042 - @alice (since 2024-01-15)
• TODO-038 - @bob (since 2024-01-14)

Recent Decisions:
• [2024-01-15] JWT vs Sessions - chose JWT (@alice)

Run 'cat _project_specs/team/state.md' for full details.

If Solo Project

👤 Solo Project Detected

Git contributors found:
• [email protected] (142 commits)
• [email protected] (38 commits)  ← Recent activity

This project has multiple git contributors but no team coordination.

Would you like to:
1. Convert to team project (adds team state management)
2. Keep as solo project (no changes)

Phase 2: Convert to Team Project

If user chooses to convert:

Step 1: Create Team Structure

mkdir -p _project_specs/team/handoffs

Step 2: Create state.md

# Team State

*Last synced: [TIMESTAMP]*

## Active Sessions

| Contributor | Working On | Started | Files Touched | Status |
|-------------|------------|---------|---------------|--------|
| - | - | - | - | - |

## Claimed Todos

| Todo | Claimed By | Since | ETA |
|------|------------|-------|-----|
| - | - | - | - |

## Recently Completed (Last 48h)

| Todo | Completed By | When | PR |
|------|--------------|------|-----|
| - | - | - | - |

## Conflicts to Watch

| Area | Contributors | Notes |
|------|--------------|-------|
| - | - | - |

## Announcements

- [DATE] Project converted to team coordination mode

Read the full file on GitHub · 289 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. 10d ago First seen · 289 lines · 0 tokens per session scan A 0dd907897c6e

Subscribe to this mod's changes

check-contributors is a command published in the GitHub repository alinaqi/maggy (706 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,450 tokens. 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-30.