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/grainulation/wheatWrote 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/grainulation/wheat/status)<a href="https://agentmods.dev/commands/grainulation/wheat/status"><img src="https://agentmods.dev/badge/commands/grainulation/wheat/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/grainulation/wheat/status"><img src="https://agentmods.dev/badge/commands/grainulation/wheat/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.00000 | $0.00425 |
| Opus 5.5 | $0.00000 | $0.00170 |
| Sonnet 5.5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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.
What it actually says
/status — Render the sprint dashboard
You are generating the current status dashboard for this Wheat sprint.
Process
-
Run the compiler:
npx @grainulation/wheat compile --summary -
Read compilation.json for all dashboard data.
-
Read git log for recent activity:
git log --oneline -20 claims.json -
Generate dashboard HTML: Create/update
output/dashboard.html— a self-contained dashboard page. The dashboard must show:Header: Sprint question, current phase, compilation status (ready/blocked), days since initiation
Phase Progress: Visual progress through define -> research -> prototype -> evaluate -> compile. Show which phases have claims.
Evidence Strength by Topic: For each topic in coverage, show:
- Topic name
- Number of claims
- Highest evidence tier (with color coding: green=tested/production, amber=documented, red=web/stated)
- Visual bar representing depth
Conflict Status:
- Resolved conflicts with winner/loser and reason
- Unresolved conflicts highlighted as blockers
- "Compilation readiness" indicator
Connected Sources: List any connectors from meta
Recent Activity: From git log — the sprint timeline
Claim Inventory: Grouped by topic, showing type, evidence tier, and status for each claim
-
Also print a text summary to the terminal so the user gets immediate feedback without opening a file.
Git commit
Only commit if the dashboard changed meaningfully. Don't commit for a status-only check.
Commit: wheat: /status — updated dashboard
Tell the user
- Print the text summary (phase, claim counts, conflicts, readiness)
- Point them to
output/dashboard.htmlfor the full visual dashboard - Suggest next actions based on what's needed (resolve conflicts, fill coverage gaps, etc.)
$ARGUMENTS
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 · 61 lines · 0 tokens per session scan A 67c1d6a1d2ff
status is a command published in the GitHub repository grainulation/wheat (20 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 425 tokens. 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-30.
Other commands, from other repositories
mcptoon-setup
Set up or repair the mcptoon CLI for this machine (install, verify, diagnose).
safe-build
Build the application for development or production.
local
Command "local" from getsentry/toolkit, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
debug-files
Command "debug-files" from getsentry/toolkit, covering examples, inspect a debug information file (auto-detects the format), bundle jvm sources with a debug id, exclude additional directories and output as json.
auth
Command "auth" from getsentry/toolkit, covering examples, oauth login (recommended), token login, read-only oauth login and custom oauth scopes.
feedback
Modern User Feedback is stored as Feedback issues. The command always limits issue searches to issue.category:feedback; it does not use the legacy User Reports API.