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/zhyx12/projtool/watch-runsgit clone --depth 1 https://github.com/zhyx12/projtoolWrote 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/zhyx12/projtool/watch-runs)<a href="https://agentmods.dev/commands/zhyx12/projtool/watch-runs"><img src="https://agentmods.dev/badge/commands/zhyx12/projtool/watch-runs.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.00024 | $0.00742 |
| Opus 5 | $0.00012 | $0.00371 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
watch-runs 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/watch-runs — caretaker loop for active runs
Watch every non-terminal run of this project until all reach a terminal state, without the user having to ask "怎么样了".
Protocol
- Inventory.
mcp__projtool__list_run_statuses(experiment_id=...)for each experiment with active runs (start frommcp__projtool__list_runsif unsure). Note each run's phase,progress_age_s, andstalled_suspect. - Close what already exited. Newly exited runs (exit sentinel
present):
mcp__projtool__finalize_runs(experiment_id=..., then=<policy>)— one call per experiment, one journal commit per batch. - Report briefly. One line per active run: run_id tail, phase,
progress age. Flag
stalled_suspect=trueruns — check theirprogress_sourcesbefore declaring a stall (pool launchers with declaredprogress_pathsoften show a fresh source behind a quiet parent log). - Schedule the next check with ScheduleWakeup (or your harness's
scheduler): first check ~5 min after launch, then 15 → 30 → 45 min
as runs prove stable. NEVER busy-wait or run
while true; do sshloops. - Repeat 1–4 on each wake until no non-terminal runs remain.
- Finish. Summarize outcomes (per-status counts, headline metrics
from
compare_runs), confirm the instance policy took effect (list_instances— nothing billing idle), and suggest/retrospectiveto distill findings.
Completion by artifact, not just process exit
Some runs signal "done" by dropping a file — metrics.json, a
.ok/.done sentinel — rather than by the process exiting, so their
exit sentinel may never land on the schedule you expect. For those runs,
treat the expected artifact's presence as the completion signal.
On EACH scheduled wake (step 4), probe for it once — a single
mcp__projtool__read_remote_file(...) or
mcp__projtool__remote_exec(command="test -f <path> && echo DROPPED")
call, using the run's declared outputs / progress_paths when present.
One probe per wake, then let the schedule pace you.
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 · 62 lines · 24 tokens per session scan A 499262a7a875
watch-runs is a command published in the GitHub repository zhyx12/projtool (1 stars, last pushed 20d ago), licensed MIT. It adds 24 tokens to every session and 742 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.