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 rules/homenshum/nodebenchai/agent_run_verdict_workflowgit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWhat 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.00449 | $0.00449 |
| Opus 5 | $0.00225 | $0.00225 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
agent_run_verdict_workflow 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.
What it actually says
Agent Run Verdict Workflow
Use this rule whenever a change affects agent runs, task sessions, execution traces, proof packs, verified results, citations, or operator-facing workflow UI.
Required workflow sections
- Contract + data model wiring
- Backend issue context enrichment
- Frontend live workflow panels
- Verdict exactness UI surfacing
- Tests + verification
Protocol
- Extend the existing NodeBench harness. Do not build a parallel agent platform.
- Start at the contract layer: session shape, verdict shape, UI shape.
- Prefer deriving verdict state from existing session and trace metadata before adding new persistence.
- Enrich backend context from decisions, verification checks, evidence, approvals, source refs, and drift.
- Put the operator summary above the raw trace drill-down.
- Keep verdicts bounded and exact:
verified,provisionally_verified,needs_review,awaiting_approval,failed,in_progress. - Always surface open issues and next actions when the run is not fully verified.
Progressive disclosure requirement
If the run is expected to resolve tool usage itself, prefer using or surfacing:
discover_toolssmart_select_toolsget_tool_quick_refget_workflow_chainfindTools
Verification floor
npx convex codegennpx tsc --noEmit- targeted tests for derivation and UI
npm run buildnpm run dogfood:verify:smokewhen the UI changed
Anti-patterns
- Treating
completedas equivalent toverified - Shipping a verdict badge with no evidence logic
- Hiding next actions in raw traces
- Stopping after one layer when the workflow spans contract, backend, UI, and verification
Canonical reference
docs/agents/AGENT_RUN_VERDICT_WORKFLOW.md
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 · 50 lines · 449 tokens per session scan A 7a630a744668
agent_run_verdict_workflow is a cursor rule published in the GitHub repository HomenShum/NodeBenchAI (14 stars, last pushed 19d ago), licensed MIT. It adds 449 tokens to every session, about $0.0022 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-30.
Other cursor rules, from other repositories
long-running-agents
Best practices for long-running agents (initializer/coding pattern, incremental progress, clean state).
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.