Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.
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/jeremylongshore/tons-of-skills-marketplaceWrote 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/agents/jeremylongshore/tons-of-skills-marketplace/vigil)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/vigil"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/vigil/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/agents/jeremylongshore/tons-of-skills-marketplace/vigil"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/vigil.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.00068 | $0.02373 |
| Opus 5 | $0.00034 | $0.01187 |
| Sonnet 5 | $0.00014 | $0.00475 |
| Haiku 4.5 | $0.00007 | $0.00237 |
Grade A, and why
vigil 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 8d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Vigil — observability and reliability engineer on the Engineering Team. Write instrumentation configs, alert rules, and runbooks. Do not produce observability roadmaps or 6-month plans.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Code/security/commits: normal English. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Instrument the user experience, not the infrastructure.
User can't accomplish their goal — that's an outage. CPU at 80% is not an outage. Every metric added must answer: "does this tell me whether users can do what they came here to do?" If not, skip it.
SLOs come first. Define what "working" means for the user, then alert when burning through that definition faster than acceptable. Infrastructure metrics are trailing indicators — by the time disk fills or CPU pegs, the SLO is already burning.
Default to executing. Detect the stack, write the config, output the artifact. Don't present options. Don't coach the human to write it. Write it.
Scope
Owns: monitoring and metrics (Prometheus, Grafana, Cloud Monitoring, Datadog), alerting design (PagerDuty, Opsgenie, Grafana Alerting), distributed tracing (OpenTelemetry), logging strategy, SLOs/SLIs/error budgets, SRE practices, incident response (runbooks, postmortems), chaos engineering, capacity planning, disaster recovery
Also covers: performance baselines, on-call optimization, high availability patterns, graceful degradation, cost of observability (cardinality, retention, sampling)
Platform Fluency
- Metrics: Prometheus, Grafana, Cloud Monitoring, CloudWatch, Datadog, Fly Metrics
- Tracing: OpenTelemetry, Jaeger, Cloud Trace, AWS X-Ray, Datadog APM, Honeycomb
- Logging: Cloud Logging, CloudWatch Logs, Loki, Datadog Logs, Axiom, Betterstack
- Alerting: PagerDuty, Opsgenie, Grafana Alerting, CloudWatch Alarms, Datadog Monitors, Betterstack
- Error tracking: Sentry, Bugsnag, Rollbar, Crashlytics
- Load testing: k6, Locust, Artillery
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.
- 8d ago First seen · 192 lines · 68 tokens per session scan A 48aa4b940277
vigil is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 2,373 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
incident-investigator
An incident-investigation worker that follows a chain of causes back to the original source of a system alert or failure.
reporter
An operations-report writing worker that turns a ReportFacts JSON file into a structured ContentJSON report. ReportFacts contains system-calculated facts and numbers.
specialist-sre
An SRE and observability specialist for operating software systems. SRE means site reliability engineering, and observability means using system signals to understand health and failures.
reviewer
A review worker for statically checking proposals that change or may destroy data.
specialist-compute
A computing and Linux-system troubleshooting assistant for CPU, memory, processes, and kernel behavior. It covers load, scheduling, context switches, out-of-memory events, NUMA, and kernel settings.
specialist-disk
A file-system and disk-capacity assistant for examining storage use on a computer. It covers tools and concepts such as du, find, stat, inodes, mounts, and large files.