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/wessamfathi/suhail/statusgit clone --depth 1 https://github.com/wessamfathi/suhailWrote 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/wessamfathi/suhail/status)<a href="https://agentmods.dev/commands/wessamfathi/suhail/status"><img src="https://agentmods.dev/badge/commands/wessamfathi/suhail/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.00017 | $0.00361 |
| Opus 5 | $0.00009 | $0.00180 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
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 3d 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
/su:status — Suhail status dashboard
You are printing the current Suhail run's status. This command takes no arguments. It reads .suhail/STATUS.md and emits it verbatim. It is strictly read-only: it never advances state, dispatches a subagent, or writes any file.
On every invocation
- No active run. Attempt to Read
.suhail/state.json. If it does not exist, end with one sentence: "No active Suhail run found — run/su:go <plan-path>to start one." - Status not yet rendered. If
.suhail/state.jsonexists but.suhail/STATUS.mddoes not, end with one sentence: "A run exists butSTATUS.mdhas not been rendered yet — run/su:goto advance one tick and regenerate it." - Emit. Read
.suhail/STATUS.mdand emit its contents verbatim to the user. Do not summarize, reformat, or annotate. End the turn.
Don't
- Do not advance state, dispatch any subagent, or write any file. This command is read-only.
- Do not accept any arguments. This command is zero-argument; ignore
$ARGUMENTSentirely. - Do not regenerate
STATUS.mdyourself — that issuhail-write's job, triggered by/su:go. If it is stale or missing, point the user at/su:go. - Do not echo
state.jsoninstead ofSTATUS.md.STATUS.mdis the human-readable view.
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.
- 3d ago First seen · 21 lines · 17 tokens per session scan A 3706d6e113ca
status is a command published in the GitHub repository wessamfathi/suhail (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 361 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
beads-onboard
Run the interactive beads-onboard interview in the current project to generate beads conventions (AGENTS.md translation matrix, labels.md, reference.md, starter formula, pre-seeded bd remember entries).
resume
Load existing handoff context to continue work.
uw-cmd-plan
Break a feature or sprint into actionable tasks with clear acceptance criteria.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
whats-next
Show current project status and suggest next steps.
roadmap
Generate or update a per-release roadmap from the PRD and analysis documents. Triages features, groups into phases, and produces a structured roadmap.