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/ArtemioPadilla/agent-triforceWrote 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/artemiopadilla/agent-triforce/status)<a href="https://agentmods.dev/commands/artemiopadilla/agent-triforce/status"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/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/commands/artemiopadilla/agent-triforce/status"><img src="https://agentmods.dev/badge/commands/artemiopadilla/agent-triforce/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.00457 |
| Opus 5 | $0.00006 | $0.00229 |
| Sonnet 5 | $0.00003 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 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.
What it actually says
Display the current Agent Triforce workflow status. This command is read-only -- it never modifies state.
Read and present the following information:
1. Workflow State
Read docs/workflow-state.json (if it exists) and display:
- Current Run: Feature name, run ID, when it started
- Active Agent: Which agent is currently working (prometeo-pm, forja-dev, centinela-qa), or "none" if idle
- Current Phase: SIGN_IN, IN_PROGRESS, TIME_OUT, or SIGN_OUT
- Phase History: List all phases in the current run with their agent, phase, and completion status
- Checklist Progress: For each checklist in the current phase, show items completed vs pending vs failed
- Blockers: List any active blockers that are preventing progress
If no workflow state file exists, report "No active workflow. Start one with python3 tools/workflow-tracker.py start <feature>."
2. Most Recent Handoff
Check docs/handoffs/ for the most recent handoff artifact (by filename timestamp). If found, show:
- From agent -> To agent
- Summary of "What was done"
- Any open questions
If no handoffs directory exists, skip this section.
3. Session Analytics
Read the most recent file in docs/analytics/ (if any exist). Display running totals:
- Estimated tokens per agent
- Estimated session cost
- Number of checklists run
- Number of findings logged
If no analytics data exists, show "No session analytics available. Run python3 tools/session-tracker.py report after a workflow session."
4. System Health Summary
Provide a quick health check:
- Check if
TECH_DEBT.mdhas any Critical/High severity active items - Check if any review in
docs/reviews/has verdict "CHANGES REQUIRED" - Report overall status: HEALTHY, WARNING, or CRITICAL
Format the output clearly with section headers. Use plain text formatting suitable for terminal display.
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 · 49 lines · 13 tokens per session scan A 137adf9195d7
status is a command published in the GitHub repository ArtemioPadilla/agent-triforce (3 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 457 once invoked, about $0.0001 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
dashboard
Starts the live web dashboard for the current fellowship — quest/scout progress, gate approvals, and event history — in the background, and prints the URL.
mega-status
Show detailed status of mega-plan execution including feature progress and story completion. Usage: /plan-cascade:mega-status.
hybrid-status
Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion percentage, and recent activity logs.
hybrid-complete
Complete Hybrid Ralph task in worktree, verify all stories complete, commit code changes (excluding planning files), merge to target branch, and cleanup worktree directory. Can be run from any directory.
OPSX: Fast Forward
Create a change and generate all artifacts needed for implementation in one go.
OPSX: Bulk Archive
Archive multiple completed changes at once.