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/khanh-vu/claude-force/statusgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/status)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/status"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/status.svg" alt="Measured on agentmods" 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 | $0.00006 | $0.01013 |
| Opus 5 | $0.00003 | $0.00507 |
| Sonnet 5 | $0.00001 | $0.00203 |
| Haiku 4.5 | $0.00001 | $0.00101 |
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 5d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Command
Display the current state of your Claude multi-agent session.
Information Displayed
Task Information
- Current task title and objective
- Task status (Not Started/In Progress/Complete)
- Priority and type
- Key requirements overview
Session Progress
- Session ID and start time
- Active workflow (if any)
- Agents completed vs total
- Current agent (if in progress)
- Estimated completion time
Recent Activity
- Last 5 agent executions
- Timestamps and status
- Any blockers or issues
Quality Status
- Validation status of current work.md
- Scorecard pass/fail summary
- Open issues or warnings
Next Steps
- Recommended next agent
- Any pending dependencies
- Blockers to resolve
Output Format
## Session Status
**Session**: 1
**Started**: 2025-11-13 09:00
**Duration**: 2 hours 15 minutes
**Status**: 🟡 In Progress
---
## Current Task
**Title**: Build Product Catalog UI
**Priority**: 🔴 High
**Type**: Feature
**Status**: In Progress (60% complete)
**Objective**: Create responsive product catalog with filters and search
---
## Workflow Progress
**Workflow**: full-stack-feature
**Progress**: 5 of 8 agents complete (62%)
✅ frontend-architect (Complete)
✅ database-architect (Complete)
✅ backend-architect (Complete)
✅ python-expert (Complete)
✅ ui-components-expert (Complete)
🔄 frontend-developer (In Progress)
⏳ qc-automation-expert (Pending)
⏳ deployment-integration-expert (Pending)
---
## Quality Status
**Last Validation**: 2025-11-13 10:30
**Status**: ✅ All Checks Pass
- Scorecard: 12/12 PASS
- Write Zone: Updated
- Secrets: None detected
- Format: Valid
---
## Recent Activity
| Time | Agent | Status | Duration |
|------|-------|--------|----------|
| 10:30 | ui-components-expert | ✅ Complete | 25 min |
| 10:05 | python-expert | ✅ Complete | 20 min |
| 09:45 | backend-architect | ✅ Complete | 30 min |
| 09:15 | database-architect | ✅ Complete | 18 min |
| 09:00 | frontend-architect | ✅ Complete | 22 min |
---
## Blockers & Issues
⚠️ 1 issue requires attention:
- **B-001**: API key from vendor pending
- Impact: Medium
- Blocking: deployment-integration-expert
- Status: Waiting for response
---
## Next Steps
1. **Immediate**: Complete frontend-developer implementation
2. **Next Agent**: qc-automation-expert
3. **After That**: deployment-integration-expert
4. **Blockers**: Resolve B-001 before final deployment
**Estimated Completion**: 1.5 hours
---
## Artifacts Produced
📄 **In work.md**:
- Frontend architecture brief
- Database schema (DDL)
- API specification (OpenAPI)
- Python ETL scripts
- React components (ProductCard, FilterBar, SearchBox)
📁 **Separate Files**:
- None yet
---
## Recommendations
💡 **Tips**:
- Run validation before proceeding to next agent
- Review Write Zones for context
- Ensure all acceptance criteria addressed
- Consider break after frontend-developer completes
---
**Last Updated**: 2025-11-13 11:00
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.
- 5d ago First seen · 208 lines · 6 tokens per session scan A 762c89f63b9f
status is a command published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It adds 6 tokens to every session and 1,013 once invoked, about $0.0000 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.