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/chriscarrollsmith/taskqueue-mcpWrote 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/rules/chriscarrollsmith/taskqueue-mcp/errors)<a href="https://agentmods.dev/rules/chriscarrollsmith/taskqueue-mcp/errors"><img src="https://agentmods.dev/badge/rules/chriscarrollsmith/taskqueue-mcp/errors/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/rules/chriscarrollsmith/taskqueue-mcp/errors"><img src="https://agentmods.dev/badge/rules/chriscarrollsmith/taskqueue-mcp/errors.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.00000 | $0.00615 |
| Opus 5.5 | $0.00000 | $0.00246 |
| Sonnet 5.5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
errors 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 1mo 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
Error Flow
graph TD
subgraph Core_Logic
FS[FileSystemService: e.g., FileReadError] --> TM[TaskManager: Throws App Errors, e.g., ProjectNotFound, TaskNotDone]
TM -->|App Error with code ERR_xxxx| CLI_Handler["cli.ts Command Handler"]
TM -->|App Error with code ERR_xxxx| ToolExec["toolExecutors.ts: execute"]
end
subgraph CLI_Path
CLI_Handler -->|App Error| CLI_Catch["cli.ts catch block"]
CLI_Catch -->|Error Object| FormatCLI["client errors.ts formatCliError"]
FormatCLI -->|"Error [ERR_xxxx]: message"| ConsoleOut["console.error Output"]
end
subgraph MCP_Server_Path
subgraph Validation_Layer
ToolExecVal["toolExecutors.ts Validation"] -->|App Error, e.g., MissingParameter| ExecToolErrHandler
end
subgraph App_Execution
ToolExec -->|App Error with code ERR_xxxx| ExecToolErrHandler["tools.ts executeToolAndHandleErrors catch block"]
ExecToolErrHandler -->|Map AppError to Protocol Error or Tool Result| ErrorMapping
ErrorMapping -->|"If validation error (ERR_1xxx)"| McpError["Create McpError with appropriate ErrorCode"]
ErrorMapping -->|"If business logic error (ERR_2xxx+)"| FormatResult["Format as isError true result"]
McpError -->|Throw| SDKHandler["server index.ts SDK Handler"]
FormatResult -->|"{ content: [{ text: Error [ERR_xxxx]: message }], isError: true }"| SDKHandler
end
SDKHandler -- Protocol Error --> SDKFormatError["SDK Formats as JSON-RPC Error Response"]
SDKHandler -- Tool Result --> SDKFormatResult["SDK Formats as JSON-RPC Success Response"]
SDKFormatError -->|"{ error: { code: -326xx, message: ... } }"| MCPClient["MCP Client"]
SDKFormatResult -->|"{ result: { content: [...], isError: true } }"| MCPClient
end
Explanation of Updated Error Flow and Transformations:
Errors are consistently through a unified AppError system:
-
Validation Errors (
ERR_1xxxseries)- Used for validation issues (e.g., MissingParameter, InvalidArgument)
- Thrown by tool executors during parameter validation
- Mapped to protocol-level McpErrors in
executeToolAndHandleErrors
-
Business Logic Errors (
ERR_2xxxand higher)- Used for all business logic and application-specific errors
- Include specific error codes
- Returned as serialized CallToolResults with
isError: true
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.
- 1mo ago First seen · 57 lines · 615 tokens per session scan A cba4f12da133
errors is a cursor rule published in the GitHub repository chriscarrollsmith/taskqueue-mcp (71 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 615 tokens. 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
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
modus-checkbox-value-inversion-react-short
Critical bug fix for ModusWcCheckbox value property inversion.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.