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 skills add spencerpauly/awesome-cursor-skills --skill monitoring-terminal-errorsgit clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skillsWrote 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/spencerpauly/awesome-cursor-skills/monitoring-terminal-errors)<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/monitoring-terminal-errors"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/monitoring-terminal-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/skills/spencerpauly/awesome-cursor-skills/monitoring-terminal-errors"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/monitoring-terminal-errors.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00035 | $0.00561 |
| Opus 5 | $0.00017 | $0.00280 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
monitoring-terminal-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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- monitoring-terminal-errors — 86% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring Terminal Errors
Continuously watch a running process (dev server, test runner, build) for errors and fix them as they appear.
Workflow
1. Identify the Terminal
List terminal files and find the one running the target process:
head -n 10 <terminals_folder>/*.txt
Look for terminals running dev servers (npm run dev, pnpm dev, python manage.py runserver, etc.).
2. Read Terminal Output
Read the full terminal file content. Search for error patterns:
- Stack traces:
at <function> (<file>:<line>:<col>) - Node.js:
Error:,TypeError:,ReferenceError:,ENOENT,ECONNREFUSED - Python:
Traceback (most recent call last):followed byFile "<path>", line <n> - React/Next.js:
Unhandled Runtime Error,Error: ...,Module not found - Build errors:
ERROR in,Failed to compile,SyntaxError - Vite:
[vite] Internal server error: - TypeScript:
error TS\d+:
3. Extract the Source Location
From the stack trace, extract:
- File path
- Line number
- Error message
For Node.js: at functionName (/path/to/file.ts:42:10)
For Python: File "/path/to/file.py", line 42, in function_name
4. Navigate and Fix
- Read the identified file around the error line
- Understand the error (missing import, type mismatch, undefined variable, etc.)
- Apply the fix
- Re-read the terminal file to confirm the server recovered (hot reload should pick it up)
5. Loop
If the server is still showing errors after the fix, repeat from step 2. Stop when:
- The terminal shows a clean "compiled successfully" or equivalent
- No new errors appear in the output
- You've made 5 attempts without resolution (report to user)
Tips
- Check for
exit_codein the terminal file footer — if present, the process has crashed entirely and needs a restart - Some errors cascade — fix the first/root error and the rest often disappear
- For HMR errors, the fix might just be saving the file again to trigger a rebuild
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.
- 10d ago First seen · 64 lines · 35 tokens per session scan A 1eb58f041ad3
monitoring-terminal-errors is a skill published in the GitHub repository spencerpauly/awesome-cursor-skills (768 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 35 tokens to every session and 561 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.