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/zywkloo/wtcraftWrote 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/zywkloo/wtcraft/statuswt)<a href="https://agentmods.dev/commands/zywkloo/wtcraft/statuswt"><img src="https://agentmods.dev/badge/commands/zywkloo/wtcraft/statuswt/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/zywkloo/wtcraft/statuswt"><img src="https://agentmods.dev/badge/commands/zywkloo/wtcraft/statuswt.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.00047 |
| Opus 5.5 | $0.00000 | $0.00019 |
| Sonnet 5.5 | $0.00000 | $0.00009 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
statuswt 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
You are checking the status of all active worktree task files in the project.
Run the following command to display the task status table in the terminal:
wtcraft status
Explain the output to the user clearly.
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 · 9 lines · 0 tokens per session scan A d686a48f9b5b
statuswt is a command published in the GitHub repository zywkloo/wtcraft (2 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 47 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-31.
Other commands, from other repositories
story-pack
A command that creates a YAML execution pack for one numbered software work item, called a Story.
story-full-exec
A batch command for executing several numbered software work items, called Stories, from their YAML instruction files.
story
A command that implements one software Story from a required YAML execution plan. The plan is the only source it uses for the Story’s rules, files, interfaces, tests, and checks.
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
rclone_test_changenotify
Log any change notify requests for the remote passed in.
tree
Emit a compact indented view of the active task hierarchy and refresh state/task-tree.json. This is the primary tool for understanding the board's shape before adding new work.