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/thread-closegit clone --depth 1 https://github.com/zhyx12/projtoolWhat 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.00041 | $0.00710 |
| Opus 5 | $0.00020 | $0.00355 |
| Sonnet 5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
thread-close 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 yesterday.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/thread-close — conclude or abandon a research thread
A thread ends one of two ways: concluded (it reached a verdict worth pinning) or abandoned (a dead end, closed with a reason). Ask which the user wants if it isn't clear. Never auto-close anything on their behalf.
If registry/ under the docs root is absent (paths.docs_dir in
.proj-tool/project.toml, docs/ by default) there is nothing to close — the
project predates the registry. Explain that and point at /thread-new (to
start lineage now) or /migrate-docs (to adopt the old plans/ + exp/
layout first).
Conclude
- Resolve the thread with
mcp__projtool__thread_tree. If the thread ispaused, it cannot conclude directly — resume it first (thread_status(new_status="active")), then proceed. The registry now reflects run outcomes: launching/finalizing runs advances each experimentplanned→running→finalized, sothread_treeshows real run counts and statuses. For a non-terminal experiment that will never run — a plan superseded before launch, or work folded into a sibling — close it explicitly withmcp__projtool__experiment_status(experiment=<slug|id>, new_status="finalized", no_run_note="…"), ornew_status="abandoned"for a dead end. The run manifests (list_runs/compare_runs) remain the fine-grained truth about individual runs. - Gather the evidence:
findings.md, the tail ofjournal.md,mcp__projtool__compare_runs, and the relevant reports. - Write
threads/<slug>/conclusion.mdciting pinned evidence: therun_ids that settle it, report paths, and headline metrics inline (so the verdict survives even if outputs are later deleted). Commit narrowly in the docs repo —git addonly that file. - Record the verdict.
mcp__projtool__thread_status(thread=<slug>, new_status="concluded", conclusion_doc="threads/<slug>/conclusion.md"). The tool requiresconclusion_docto exist on disk — write it before the call.
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.
- yesterday First seen · 53 lines · 41 tokens per session scan A 65ba17452a09
thread-close is a command published in the GitHub repository zhyx12/projtool (1 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 710 once invoked, about $0.0002 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.