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/reluctantfuturist/loyal-wingmanWrote 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/reluctantfuturist/loyal-wingman/project-status)<a href="https://agentmods.dev/commands/reluctantfuturist/loyal-wingman/project-status"><img src="https://agentmods.dev/badge/commands/reluctantfuturist/loyal-wingman/project-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/reluctantfuturist/loyal-wingman/project-status"><img src="https://agentmods.dev/badge/commands/reluctantfuturist/loyal-wingman/project-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.00018 | $0.00635 |
| Opus 5 | $0.00009 | $0.00318 |
| Sonnet 5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
project-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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/project-status
Display progress metrics for active writing project.
Usage
/project-status # Default project (first found)
/project-status [ProjectName] # Specific project
/project-status --all # All projects
/project-status --seeds # Include scene seeds count
Process
Step 1: Identify Project
Scan 10_Projects/ for project folders containing Scenes/ subdirectory.
If no project specified, use first project found or ask user to specify.
Step 2: Gather Metrics
For each chapter/scene file:
From frontmatter:
status: draft | review | finalword_count: if presenttimeline_date: scene date
Calculated:
- Word count (if not in frontmatter)
- Last modified date
Step 3: Display Progress
## [Project Name] - Progress
| Chapter | Words | Status | Last Modified |
|---------|-------|--------|---------------|
| Ch 1 | 4,325 | final | Nov 17 |
| Ch 2 | 3,890 | final | Dec 10 |
| Ch 3 | 1,245 | draft | Jan 2 |
**Total:** 9,460 words
**Chapters:** 3 (2 final, 0 review, 1 draft)
### Timeline Coverage
- Earliest scene: [date]
- Latest scene: [date]
### Recent Activity
- [Most recent change description]
### Blockers
[Any TODO tags or blocking notes from frontmatter]
Step 4: Optional Additions
With --seeds flag:
### Scene Seeds
- [count] seeds in 10_Projects/Scene_Seeds/
- [count] potentially for this project (based on tags/mentions)
With --all flag: Show summary table for all projects:
| Project | Chapters | Words | Status |
|---------|----------|-------|--------|
| Project_A | 3 | 9,460 | Active |
| Project_B | 10 | 45,230 | Revision |
| Project_C | 0 | 0 | Planning |
With --series flag:
### Series Planning
Files in 10_Projects/Series_Planning/:
- [file list with summaries]
Status Definitions
| Status | Meaning |
|---|---|
| draft | Initial writing, not reviewed |
| review | Ready for editorial pass |
| final | Approved, publication-ready |
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 · 111 lines · 18 tokens per session scan A 329e9e392fe2
project-status is a command published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 18 tokens to every session and 635 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.