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 soumyachk101/VibeLens --skill console-triagegit clone --depth 1 https://github.com/soumyachk101/VibeLensWrote 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/soumyachk101/vibelens/console-triage)<a href="https://agentmods.dev/skills/soumyachk101/vibelens/console-triage"><img src="https://agentmods.dev/badge/skills/soumyachk101/vibelens/console-triage/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/soumyachk101/vibelens/console-triage"><img src="https://agentmods.dev/badge/skills/soumyachk101/vibelens/console-triage.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.00084 | $0.01209 |
| Opus 5 | $0.00042 | $0.00605 |
| Sonnet 5 | $0.00017 | $0.00242 |
| Haiku 4.5 | $0.00008 | $0.00121 |
Grade A, and why
console-triage 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Console triage
Target: $ARGUMENTS (if empty, ask for the URL).
A page that looks correct in the screenshot and still logs a hydration mismatch is broken. The pixels were produced by a client re-render that threw away the server markup; the next state change, or the next visitor on a slow connection, gets a different page. Never close a diagnostics issue because the screenshot looks fine.
Steps
-
Capture with
inspect_localhost_ui. Usedelay: 3000— most diagnostics fire during hydration and data fetching, so a short wait under-reports.fullPageis irrelevant here; leave it off unless lazy-loaded sections below the fold are what you are chasing. -
Read
summaryfirst:consoleErrors,consoleWarnings,uncaughtPageErrors,failedRequests. Those four counts are your work list. If all four are zero, say so and stop — do not go hunting for problems. -
Group by root cause, not by line. One bad prop can emit forty identical warnings. Collapse them into a single item with a count, and use
consoleLogs[].location(file:line:column) to pin the origin. -
Triage each group. The recurring ones and what they actually mean:
-
React hydration mismatch (
Hydration failed,Text content did not match,did not match server-rendered HTML). Server and client rendered different trees. Usual causes:Date/Math.random/toLocaleStringat render time, readingwindow/localStorageduring the first render,typeof window !== 'undefined'branching in the returned markup, or invalid nesting the parser rewrites (<div>inside<p>,<p>inside<p>). Fix by moving the non-deterministic read intouseEffect, or gating it behind a mounted flag. Highest severity: it invalidates the whole render. -
Undefined access during render (
Cannot read properties of undefined,x is not a function) — usually inuncaughtPageErrors, and usually paired with a blank or partial screenshot. Data arrived later than the component assumed, or a.mapran onundefined. Fix with the loading/empty state the component is missing, not with a blanket optional chain that hides the real hole.
-
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.
- 11d ago First seen · 97 lines · 84 tokens per session scan A f57168bfb859
console-triage is a skill published in the GitHub repository soumyachk101/VibeLens (0 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 1,209 once invoked, about $0.0004 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-31.
Other skills, from other repositories
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
debugging-and-error-recovery
Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need to figure out what broke and why — a systematic approach to finding and fixing the root cause rather than…
sdlc-bug-report
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
distributed-tracing
Implement distributed tracing with OpenTelemetry, Tempo/Jaeger — instrumentation, sampling, and trace-to-log correlation. Use when the user asks about distributed tracing, OpenTelemetry setup, span instrumentation, trace propagation, or connecting traces to logs and metrics.
pod-troubleshooting
Systematic diagnosis of Kubernetes pod failures — CrashLoopBackOff, OOMKilled, Pending, ImagePullBackOff, and service connectivity issues. Use when the user encounters pods not starting, container restart loops, scheduling failures, or service unreachability in a K8s cluster.