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 skills add MadAppGang/claude-code --skill statusgit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/skills/madappgang/claude-code/status)<a href="https://agentmods.dev/skills/madappgang/claude-code/status"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/status/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/skills/madappgang/claude-code/status"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/status.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.00013 | $0.01263 |
| Opus 5.5 | $0.00005 | $0.00505 |
| Sonnet 5.5 | $0.00003 | $0.00253 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
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 1mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
plugin: conductor updated: 2026-01-20
<read_only>
This skill ONLY reads files.
It does NOT modify any conductor/ files.
For modifications, use other skills.
</read_only>
<comprehensive_scan>
Parse ALL of:
- conductor/tracks.md (index)
- conductor/tracks/*/plan.md (all plans)
- conductor/tracks/*/metadata.json (state)
</comprehensive_scan>
</critical_constraints>
<core_principles> Always end with clear "Next Action" recommendation. Don't just report status, guide next step.
<principle name="Blocker Visibility" priority="high">
Prominently display any blocked tasks.
Blockers need attention.
</principle>
</core_principles>
<phase number="2" name="Analysis">
<step>Count tasks by status: pending, in_progress, complete, blocked</step>
<step>Calculate completion percentage per track</step>
<step>Identify current phase and task</step>
<step>Find any blocked tasks</step>
</phase>
<phase number="3" name="Presentation">
<step>Display overview summary</step>
<step>Show per-track details</step>
<step>Highlight blockers if any</step>
<step>Recommend next action</step>
</phase>
Example:
- Total tasks: 15
- Completed: 6
- In Progress: 1
- Pending: 8
- Completion: 40%
</progress_calculation>
<status_priority>
Display order by priority:
1. BLOCKED tasks (need attention)
2. IN_PROGRESS tasks (current work)
3. Active tracks summary
4. Completed tracks (brief)
</status_priority>
</knowledge>
<examples>
<example name="Single Active Track">
<user_request>What's my status?</user_request>
<correct_output>
## Conductor Status
### Active Tracks: 1
**feature_auth_20260105** - User Authentication
- Progress: [========------] 53% (8/15 tasks)
- Phase: 2/4 - Core Authentication
- Current: 2.3 Create login endpoint
- Blockers: None
### Next Action
Continue task 2.3 (Create login endpoint) in feature_auth track.
Run: `conductor:implement`
</correct_output>
</example>
<example name="Multiple Tracks with Blocker">
<user_request>Show me the status</user_request>
<correct_output>
## Conductor Status
### BLOCKERS (1)
- **feature_auth_20260105** Task 2.4: "Waiting for API key from team lead"
### Active Tracks: 2
**feature_auth_20260105** - User Authentication
- Progress: [=======-------] 47% (7/15 tasks)
- Phase: 2/4 - Core Authentication
- Status: BLOCKED at 2.4
**bugfix_login_20260104** - Login redirect fix
- Progress: [==============] 100% (5/5 tasks)
- Status: Ready for review
### Next Action
Resolve blocker in feature_auth (Task 2.4) or complete review of bugfix_login.
</correct_output>
</example>
</examples>
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.
- 1mo ago First seen · 185 lines · 13 tokens per session scan A 3df7db5f5f92
status is a skill published in the GitHub repository MadAppGang/claude-code (287 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 1,263 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
progress-evaluation
Evaluates project progress by analyzing workspace structure, code completeness, and comparing against planned milestones. Outputs structured progress reports.
weekly-update
A six-to-eight-page horizontal team update presentation covering completed work, current work, blockers, metrics, requests, and thanks.
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
conductor-setup
Scaffolds the project and sets up the Conductor environment interactively.
conductor-review
Reviews a completed track against its plan and guidelines; auto-archives on pass, auto-deletes and restarts on fail.
conductor-newTrack
Plans a new track, generates spec and plan files, and registers it in the tracks registry.