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/report-newgit 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.00029 | $0.00989 |
| Opus 5 | $0.00015 | $0.00495 |
| Sonnet 5 | $0.00006 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
report-new 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 2d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the user's /report-new command.
Steps
-
Ask the user which run(s) the report covers. Accept either explicit
run_ids or "the last run", "all of exp-X", "compare runs A and B".- For implicit selectors, call
mcp__projtool__list_runswith the appropriate filters and confirm with the user before continuing. - If a run is
is_dirty=true, mention it — the report frontmatter will get aprovenance_warningsfield.
- For implicit selectors, call
-
Decide the report type and scope:
- type:
single,comparison,ablation,seed_sweep,milestone. If unsure, ask. Default for one run issingle; for >1 run on the same branch, ask whether it's an ablation or comparison; for runs spanning multiple branches, the report is a cross-branch summary. - scope:
branch(default — report belongs to one code-repo branch, filed under that branch's directory in the docs repo) orsummary(cross-branch — filed undersummary/).
- type:
-
Call
mcp__projtool__start_reportwithexperiment_id,run_ids,report_type, andscope. The tool:- Loads each run's manifest (via
load_manifest). - Generates a report frontmatter prefilled with
referencesandmetrics_inlinedskeletons, plus the cross-repo fieldsgit.branch,git.commit,git.code_repo_url,git.commit_url. - Writes the file to the docs repo (NOT to the code repo!). The path is
either
<docs_repo>/<branch_full>/<date>-<topic_slug>.md(scope=branch) or<docs_repo>/summary/<date>-<topic_slug>.md(scope=summary), where<docs_repo>=<container_root>/docs/(the independent docs git repo at the container root, alongsidecode/andoutput/). The slug is initially "TBD"; pass a real slug tocommit_reportlater.
- Loads each run's manifest (via
-
Show the user the path to the new file. Open it (with
view) so they can see the frontmatter and start drafting the body. -
Reference handling:
- When the body cites a number, also fill the corresponding field in
metrics_inlined. If a number is in the body but missing from frontmatter, that's a violation — call it out. - If the run group is >8 runs, the tool will have generated a
data/<sweep-name>.csv(alongside the report, in the same docs-repo subdirectory) instead of inlining the list; tell the user.
- When the body cites a number, also fill the corresponding field in
-
Do not commit yet. The report is a draft. Tell the user to use
/report-commit(ormcp__projtool__commit_report) once they're done.commit_reportwill:- Validate that all cited code commits are pushed to the code repo's origin.
If not, it errors with a clear instruction to
git pushfirst (cross-repo invariant). git addthe specific.mdand (if externalized) CSV files, then commits and pushes to the docs repo's current branch (resolved viagit symbolic-ref --short HEAD, never hardcoded asmain) in the docs repo (NOT the code repo).
- Validate that all cited code commits are pushed to the code repo's origin.
If not, it errors with a clear instruction to
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.
- 2d ago First seen · 74 lines · 29 tokens per session scan A fbde99067a81
report-new is a command published in the GitHub repository zhyx12/projtool (1 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 989 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.