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 whawkinsiv/solo-founder-skills --skill monitorgit clone --depth 1 https://github.com/whawkinsiv/solo-founder-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/whawkinsiv/solo-founder-skills/monitor)<a href="https://agentmods.dev/skills/whawkinsiv/solo-founder-skills/monitor"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/monitor/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/whawkinsiv/solo-founder-skills/monitor"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00092 | $0.02649 |
| Opus 5 | $0.00046 | $0.01324 |
| Sonnet 5 | $0.00018 | $0.00530 |
| Haiku 4.5 | $0.00009 | $0.00265 |
Grade A, and why
monitor 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 — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor
This skill is for production monitoring and incident response. For debugging specific bugs, use debug. For pre-launch readiness checks, use go-live. For security-specific monitoring (auth events, API abuse), use secure. For analytics and user behavior tracking, use analytics.
Don't Do Yet
- Don't pay for monitoring tools until you've outgrown the free tiers. UptimeRobot + Sentry free handles most early-stage apps.
- Don't set up DataDog, New Relic, or Grafana. These are enterprise tools. You don't need them with < 1,000 users.
- Don't build custom dashboards. Your hosting platform (Vercel, Railway) has built-in metrics. Use those first.
- Don't monitor everything. Three things matter at launch: is it up, are there errors, is it slow. That's it.
Monitoring Checklist
Basic Monitoring:
- [ ] Uptime monitoring (is site up?)
- [ ] Error tracking (are errors happening?)
- [ ] Performance monitoring (is it slow?)
- [ ] User activity (are people using it?)
- [ ] Critical alerts configured
- [ ] Check dashboard daily
See MONITORING-SETUP.md for implementation.
Why Monitor?
Without monitoring:
- Users hit errors, you don't know
- Site goes down, you find out from Twitter
- Slow performance, users leave silently
- Security issues, no alert
With monitoring:
- Errors show in dashboard immediately
- Get text when site goes down
- See performance degradation
- Catch issues before users complain
Goal: Know about problems before users tell you.
Three Essential Monitors
1. Is It Up?
Uptime monitoring - Pings your app every minute
Free tools:
- UptimeRobot (free, 50 monitors)
- Pingdom (limited free tier)
- Vercel/Netlify (built-in for deployed apps)
Setup:
1. Sign up for UptimeRobot
2. Add monitor for https://yourapp.com
3. Add your email for alerts
4. Get texted if site is down
2. Are There Errors?
Error tracking - Captures JavaScript errors and API failures
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 492 lines · 92 tokens per session scan A f70d2e9748e8
monitor is a skill published in the GitHub repository whawkinsiv/solo-founder-skills (243 stars, last pushed 15d ago), licensed MIT. It adds 92 tokens to every session and 2,649 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…