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.
git clone --depth 1 https://github.com/alinaqi/maggyWrote 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/commands/alinaqi/maggy/check-contributors)<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.
<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>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.00000 | $0.01450 |
| Opus 5 | $0.00000 | $0.00725 |
| Sonnet 5 | $0.00000 | $0.00290 |
| Haiku 4.5 | $0.00000 | $0.00145 |
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.
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
- Detect current state - Is this a solo or team project?
- Show active contributors - Who's working on what right now?
- 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
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.
- 10d ago First seen · 289 lines · 0 tokens per session scan A 0dd907897c6e
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.
Other commands, from other repositories
frappe-backend
Treat the task as Frappe backend work.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.