Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/skills/markmhendrickson/neotoma/report-error)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/report-error"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/report-error/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/skills/markmhendrickson/neotoma/report-error"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/report-error.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.00006 | $0.12456 |
| Opus 5.5 | $0.00002 | $0.04982 |
| Sonnet 5.5 | $0.00001 | $0.02491 |
| Haiku 4.5 | $0.00001 | $0.01246 |
Grade A, and why
report-error scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
const currentRepoPath = execSync('git rev-parse --show-toplevel').toString().trim(); Copies of this mod
6 near-identical copies found in the catalogue:
- report_error — 100% identical, 10 lines differ
- report-error — 98% identical, 2 lines differ
- report-error — 98% identical, 6 lines differ
- report — 97% identical, 62 lines differ
- report — 95% identical, 59 lines differ
- report — 95% identical, 58 lines differ
How it starts
The opening of the file, as written. The whole thing — 1,509 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: report-error description: Report error per foundation command. triggers:
- report error
- /report_error
- report-error
Report Error Command
Purpose
Enable agents to report errors for automated resolution by Cursor Cloud Agent. This command detects, classifies, and documents errors in a structured format for systematic resolution.
Supports cross-repo reporting: Report errors to sibling repositories (repos sharing the same parent directory) by passing the target repo name.
Command Usage
/report_error [target-repo-name] [--no-wait] [--timeout SECONDS] [--poll-interval SECONDS]
Parameters:
target-repo-name(optional): Name of sibling repository to report error to- Must be a sibling repository (shares same parent directory)
- Example: If current repo is
/Users/user/Projects/personal, targetneotomaresolves to/Users/user/Projects/neotoma - If omitted: Auto-detect target repository based on error origin (see Auto-Detection below)
--no-wait(optional): Disable wait-for-resolution mode (default: wait mode is enabled)--timeout SECONDS(optional): Maximum time to wait for resolution (default: 300 seconds / 5 minutes)--poll-interval SECONDS(optional): How often to check error status (default: 5 seconds)
Default Behavior:
- Wait mode is enabled by default - Agent will monitor error status until resolved or timeout
- Auto-detection is enabled - If target-repo-name is not provided, automatically detect target repository based on error origin
Examples:
# Auto-detect target repo and wait for resolution (default behavior)
/report_error
# Explicitly specify target repo (auto-detection disabled)
/report_error neotoma
# Disable wait mode (report and continue immediately)
/report_error --no-wait
# Custom timeout (10 minutes, default is 5 minutes)
/report_error --timeout 600
# Custom poll interval (check every 2 seconds, default is 5 seconds)
/report_error --poll-interval 2
# Explicit target repo with custom timeout
/report_error neotoma --timeout 600
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 · 1,509 lines · 6 tokens per session scan A 396b7676e57a
report-error is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 12,456 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
bernstein-alerts
Show active alerts from Bernstein - failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
ci-fixer
CI failures - read error, minimal fix, verify.
cratis-chronicle-cli-operations
Inspect and operate a running Chronicle server with the cratis CLI - contexts and connection resolution, machine-readable output, failed partitions, observers, event sequences, read models, projections and jobs, and the authorization discipline for replay, retry, quarantine clearing and other mutations. Use when the…
plumb-line-remediate
Use when applying findings from a plumb-line audit report — the builder has a report (or pasted findings) and wants the fixes made. Opt-in and separate from the audit, which is read-only and never fixes.
cratis-lens-browser-extension
Use the Cratis Lens browser extension against a running Cratis Arc application — building and side-loading it, what the Arc app must already serve for Lens to work, switching the active user and tenant, and executing a command or query from the popup. Use when setting Lens up, when Lens does not detect an Arc app, or…
cratis-arc-observable-query-http
Inspect a Cratis Arc observable query from a terminal with curl or another plain HTTP client — snapshot GET, waiting for the first result, Server-Sent Events streaming, and long polling, plus the exact query-string keys, status codes, and payload shape. Use when debugging or exploring an observable query without…