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 elisymlabs/elisym --skill site-statusgit clone --depth 1 https://github.com/elisymlabs/elisymWrote 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/elisymlabs/elisym/site-status)<a href="https://agentmods.dev/skills/elisymlabs/elisym/site-status"><img src="https://agentmods.dev/badge/skills/elisymlabs/elisym/site-status/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/elisymlabs/elisym/site-status"><img src="https://agentmods.dev/badge/skills/elisymlabs/elisym/site-status.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.00024 | $0.00219 |
| Opus 5.5 | $0.00010 | $0.00088 |
| Sonnet 5.5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
site-status 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 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.
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.
What it actually says
You are a website status checker agent.
When asked to check a website:
- Use the check_status tool with the URL
- Report status code, response time, SSL validity, and server info
- Note any redirects in the chain
IMPORTANT: Output plain text only. No markdown formatting (no #, **, -, ```, etc.). Use simple line breaks and dashes for structure.
What ships with it
1 file 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.
- 1mo ago First seen · 28 lines · 24 tokens per session scan A e523793f6402
site-status is a skill published in the GitHub repository elisymlabs/elisym (19 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 219 once invoked, about $0.0001 per session on Opus 5.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
forge-diagnose
Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".
distributed-tracing
Implement distributed tracing with Jaeger and Tempo for request flow visibility across microservices.
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
incident-responder
Expert SRE incident responder specializing in rapid problem resolution, modern observability, and comprehensive incident management.
clum-mcp
A procedure for using clum, a remote Linux operations platform that runs commands through a secure proxy rather than direct SSH. It also describes how to inspect systems, investigate failures, compare solutions, and review incidents.
application-integration-troubleshooting
Diagnoses failed, stuck, or silent Google Cloud Application Integration runs and Integration Connectors tasks using the REST API, Cloud Logging, and Cloud Monitoring. Use when an integration fails, returns HTTP 200 without doing the expected work, hangs in a suspended or retry state, or hits IAM, run-as service…