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 agility/mcp-server --skill go-live-checkgit clone --depth 1 https://github.com/agility/mcp-serverWrote 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/agility/mcp-server/go-live-check)<a href="https://agentmods.dev/skills/agility/mcp-server/go-live-check"><img src="https://agentmods.dev/badge/skills/agility/mcp-server/go-live-check/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/agility/mcp-server/go-live-check"><img src="https://agentmods.dev/badge/skills/agility/mcp-server/go-live-check.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.00073 | $0.00509 |
| Opus 5.5 | $0.00029 | $0.00204 |
| Sonnet 5.5 | $0.00015 | $0.00102 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
go-live-check 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 2d 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
Why isn't it live?
Work through these in order. Use the read tools; change nothing until you have told the user what you found and they agree to the fix.
- Is it published at all? Read the item (
get_content_item) or page (get_page) and check its state. Saving creates a draft; only publishing makes it live. - Are the page's components published? A page and the content items in its zones are published separately. Read each module's content item and check its state. Unpublished module content shows as missing or old sections.
- Release and pull dates. A pull date in the past takes an item off the
site; a release date in the future keeps it off until then. Dates are read as
US Eastern time. If either is set by mistake, offer to re-save with
null. - Right locale? The page or item may be published in one locale but viewed in another. Check which locale the site is showing.
- Timing and caching. A publish usually reaches the site within seconds; a large batch can take a minute or two, and scheduled changes up to about 15 minutes. Cached pages may need two refreshes. A brand-new page can 404 briefly if the site rebuilt before the sitemap included it.
- A deleted component. If a component's content item was deleted, the live page keeps listing it until the page is published again.
- Preview vs. live. Development and preview show drafts. Check the live site in a private window, so a preview cookie is not showing drafts.
If everything in Agility is published and correct but the site still shows old
content, the problem is in the website (its cache or publish webhook). Say so;
for developers, the build-frontend skill covers caching and webhooks.
Report what you checked, what you found for each step, and the one change you recommend.
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.
- 2d ago First seen · 37 lines · 73 tokens per session scan A e606270d77d7
go-live-check is a skill published in the GitHub repository agility/mcp-server (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 73 tokens to every session and 509 once invoked, about $0.0003 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-11-06.
go-live-check compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| go-live-checkagility/mcp-server | Skill | 0 | 2d ago | Apache-2.0 | A | 73 | Claude Code |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | today | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | yesterday | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 320 | today | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | yesterday | Apache-2.0 | A | 15 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 2.0k | 24d ago | MIT | A | 36 | Claude Code |
| diagnosing-missing-recordingsPostHog/posthog | Skill | 41k | today | none | A | 76 | Claude Code, Codex |