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/monoes/monomindWrote 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/monoes/monomind/post-task)<a href="https://agentmods.dev/commands/monoes/monomind/post-task"><img src="https://agentmods.dev/badge/commands/monoes/monomind/post-task/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/monoes/monomind/post-task"><img src="https://agentmods.dev/badge/commands/monoes/monomind/post-task.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.00014 | $0.00414 |
| Opus 5.5 | $0.00006 | $0.00166 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
hooks:post-task 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.
What it actually says
hooks post-task
Record a task outcome against its routed agent.
Usage
npx monomind hooks post-task [options]
Options
| Flag | Short | Type | Required | Description |
|---|---|---|---|---|
--task-id |
-i |
string | no | Task identifier (auto-generated if omitted) |
--success |
-s |
boolean | no | Whether task succeeded (default: true) |
--quality |
-q |
number | no | Quality score 0–1 |
--agent |
-a |
string | no | Agent that executed the task |
--format |
— | string | no | Output format: json |
Examples
# Record successful completion
npx monomind hooks post-task -i task-123 --success true
# Record failed task with quality score
npx monomind hooks post-task -i task-456 --success false -q 0.3
# Record with agent attribution
npx monomind hooks post-task -i task-789 --success true -a coder -q 0.95
# JSON output
npx monomind hooks post-task -i task-123 --success true --format json
Output
- Whether the feedback record was written, and which store took it
- Whether the routing outcome was saved
MCP Tool
mcp__monomind__hooks_post-task({
taskId: "task-123",
success: true,
quality: 0.95,
agent: "coder",
timestamp: Date.now()
})
See Also
hooks pre-task— register task starthooks metrics— view recorded routing/outcome metrics
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 · 63 lines · 14 tokens per session scan A a92a81db7c4c
hooks:post-task is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 414 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other commands, from other repositories
doctor
Health-check the harness: kernel load, MCP wiring, memory backend, host adapter.
review-diff
Review the current working diff for correctness, security, and reuse.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
prp-plan
Create comprehensive feature implementation plan with codebase analysis and pattern extraction.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
checklist
Generate a custom checklist for the current feature based on user requirements.