Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yashmody/proofhub-mcp/plugin install proofhubWrote 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/yashmody/proofhub-mcp/proofhub)<a href="https://agentmods.dev/commands/yashmody/proofhub-mcp/proofhub"><img src="https://agentmods.dev/badge/commands/yashmody/proofhub-mcp/proofhub.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.1 | $0.00043 | $0.01827 |
| Opus 5 | $0.00022 | $0.00914 |
| Sonnet 5 | $0.00009 | $0.00365 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
proofhub 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/proofhub — route a subcommand to ProofHub
You are dispatching a ProofHub action. The full invocation is:
proofhub $ARGUMENTS
- First token = subcommand:
$0 - Remaining tokens = its arguments:
$1,$2, … (indexed args use shell-style quoting, so a quoted multi-word value like"QA smoke"is a single argument).
If $ARGUMENTS is empty, do not guess — print the subcommand list at the bottom of this file and stop.
How to dispatch
Prefer the native MCP tool (mcp__proofhub__*) for every subcommand below. The server reads
PROOFHUB_ACCOUNT / PROOFHUB_API_KEY from the environment and keeps project/todolist/stageOrder
context server-side, so once the user runs use / use-list, later subcommands need no IDs.
Only fall back to the bundled CLI for subcommands that have no MCP tool (see the CLI-only table).
Map $0 to exactly one action. Pass the user's positional args through to the tool's named
parameters as shown. Do not invent arguments the user didn't supply (e.g. never fabricate a
project/todolist — the tool falls back to saved context, and will return a clear error if
context is missing). After the tool returns, report its result text plainly.
Subcommand → MCP tool
Subcommand ($0) |
Args | MCP tool | Tool arguments |
|---|---|---|---|
use |
<projectId> |
mcp__proofhub__set_context |
project: $1 |
use-list |
<todolistId> |
mcp__proofhub__set_context |
todolist: $1 |
status |
— | mcp__proofhub__get_context |
(none) |
projects |
— | mcp__proofhub__list_projects |
(none) |
lists |
[projectId] |
mcp__proofhub__list_todolists |
project: $1 (omit to use context) |
tasks |
[projectId] [todolistId] |
mcp__proofhub__list_tasks |
project/todolist only if the user gave them; else omit for context |
get |
<ticket> |
mcp__proofhub__get_task |
task: $1 |
add |
"<title>" |
mcp__proofhub__create_task |
title: $1 (pass description/due only if the user supplied them) |
find |
"<text>" |
mcp__proofhub__find_task |
text: $1 |
note |
<ticket> "<text>" |
mcp__proofhub__comment |
task: $1, body: $2 |
done |
<ticket> |
mcp__proofhub__complete |
task: $1 |
reopen |
<ticket> |
mcp__proofhub__reopen |
task: $1 |
stages |
— | mcp__proofhub__list_stages |
(none) |
stages --set |
"A,B,C" |
mcp__proofhub__set_context |
stageOrder: "<the comma list>" |
stage |
<ticket> <stageName|id> |
mcp__proofhub__set_stage |
task: $1, stage: $2 |
next |
<ticket> |
mcp__proofhub__next_stage |
task: $1 |
move |
<ticket> --to-list <id> [--to-project <id>] |
mcp__proofhub__move_task |
task: <ticket>, to_list: <id>, to_project: <id if given> |
shard |
<ticket> |
mcp__proofhub__shard_to_story |
task: $1 |
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.
- 5d ago First seen · 93 lines · 43 tokens per session scan A 8431c762e948
proofhub is a command published in the GitHub repository yashmody/proofhub-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,827 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.