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 agentmods add commands/anton-abyzov/specweave/github-statusgit clone --depth 1 https://github.com/anton-abyzov/specweaveWhat 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 | $0.00034 | $0.03339 |
| Opus 5 | $0.00017 | $0.01670 |
| Sonnet 5 | $0.00007 | $0.00668 |
| Haiku 4.5 | $0.00003 | $0.00334 |
Grade A, and why
github-status 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 2d 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check GitHub Sync Status
Display the current GitHub sync status for a SpecWeave increment.
Usage
sw:github:status [increment-id] [options]
Arguments
increment-id: Increment ID (optional, defaults to current increment)
Options
--all: Show status for all increments--verbose: Show detailed sync information--json: Output in JSON format--check-health: Run health check on sync connection
Examples
# Check current increment
sw:github:status
# Check specific increment
sw:github:status 0004
# Check all increments
sw:github:status --all
# Verbose output with full details
sw:github:status 0004 --verbose
# JSON output for scripting
sw:github:status 0004 --json
# Health check
sw:github:status --check-health
Output Format
Basic Status
📊 GitHub Sync Status: Increment 0004
Increment: 0004-plugin-architecture
Status: In Progress
Priority: P1
GitHub Issue: #130
URL: https://github.com/owner/repo/issues/130
State: Open
Labels: specweave, increment, P1, in-progress
Sync Status: ✅ Up-to-date
Last Synced: 5 minutes ago (2025-10-30 16:55:00)
Sync Count: 7
Auto-Sync: Enabled (every-task)
Progress:
- Tasks: 7/48 completed (15%)
- Week: 1 of 4 (Foundation)
- Current Task: T-008 - Implement Cursor compiler
GitHub vs Local:
✅ Progress matches
✅ Labels match
✅ Status matches
✅ No conflicts detected
Verbose Status
📊 GitHub Sync Status: Increment 0004 (Detailed)
═══════════════════════════════════════════
BASIC INFO
═══════════════════════════════════════════
Increment ID: 0004
Full Name: 0004-plugin-architecture
Title: Plugin Architecture
Status: in_progress
Priority: P1
Created: 2025-10-01 10:00:00
Duration: 29 days
═══════════════════════════════════════════
GITHUB ISSUE
═══════════════════════════════════════════
Issue Number: #130
Issue URL: https://github.com/owner/repo/issues/130
Issue State: open
Issue Created: 2025-10-01 10:15:00
Issue Updated: 2025-10-30 16:55:00
Labels:
- specweave
- increment
- P1
- in-progress
Milestone: v0.4.0 (due: 2025-11-30)
Assignees: @developer1, @developer2
Comments: 12
- 7 auto-sync comments
- 5 manual comments
Last Comment:
By: @developer2
At: 2025-10-30 16:00:00
Text: "Cursor adapter completed, moving to testing..."
═══════════════════════════════════════════
SYNC STATUS
═══════════════════════════════════════════
Sync State: ✅ Up-to-date
Last Synced: 5 minutes ago (2025-10-30 16:55:00)
Sync Method: Auto (post-task hook)
Sync Count: 7
Failed Syncs: 0
Auto-Sync Settings:
- Enabled: Yes
- Frequency: every-task
- Post Comments: Yes
- Update Checklist: Yes
- Update Labels: Yes
- Include Files: Yes
- Include Time: Yes
═══════════════════════════════════════════
PROGRESS
═══════════════════════════════════════════
Tasks: 7/48 completed (15%)
Week 1: Foundation (7/12 tasks, 58%)
✅ T-001: Plugin types
✅ T-002: Manifest schema
✅ T-003: PluginLoader
✅ T-004: PluginManager
✅ T-005: PluginDetector
✅ T-006: Adapter interface
✅ T-007: Claude installer
⏳ T-008: Cursor compiler (in progress)
⏸️ T-009: Copilot compiler
⏸️ T-010: Generic compiler
⏸️ T-011: Config schema
⏸️ T-012: Update .gitignore
Week 2: GitHub Plugin (0/10 tasks, 0%)
Week 3: Additional Plugins (0/15 tasks, 0%)
Week 4: Documentation (0/11 tasks, 0%)
Current Task: T-008
Estimated: 6 hours
Started: 2025-10-30 15:00:00
Duration: 2 hours (33% of estimate)
═══════════════════════════════════════════
COMPARISON (GitHub vs Local)
═══════════════════════════════════════════
✅ Progress: 7/48 (both sides match)
✅ Labels: All 4 labels match
✅ Status: in_progress (both sides)
✅ Comments: All synced (no missing)
No conflicts detected.
Last comparison: Just now
═══════════════════════════════════════════
METADATA
═══════════════════════════════════════════
Metadata File: .specweave/increments/0004/.metadata.yaml
GitHub Section:
issue_number: 130
issue_url: https://github.com/owner/repo/issues/130
created_at: 2025-10-01T10:15:00Z
last_synced_at: 2025-10-30T16:55:00Z
sync_count: 7
closing_comment_ids: []
Repository: owner/repo
Remote URL: https://github.com/owner/repo.git
Branch: features/0004-plugin-architecture
═══════════════════════════════════════════
HEALTH
═══════════════════════════════════════════
✅ GitHub CLI: Authenticated
✅ Repository Access: Write
✅ Issue Exists: Yes
✅ Network: Connected
✅ Rate Limit: 4,823 / 5,000 remaining
✅ Sync Hook: Installed and working
All systems operational.
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.
- 2d ago First seen · 533 lines · 34 tokens per session scan A 2ce8c7092374
github-status is a command published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 3,339 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-30.
Other commands, from other repositories
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
plan-regression-tests
Plan regression tests for existing code with it.skip statements.
export
Export the wiki (or architecture model) to markdown, HTML, JSON, or Structurizr DSL.
doc
Use this command to create a new feature doc, how-to, concept, reference, or troubleshooting guide — it scaffolds the file, frontmatter, structure, and sidebar entry.
review-teardown
Delete a review branch to free the shared Pantheon review slot.
dev-docs-update
Update dev documentation before context compaction.