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 JinNing6/Noosphere --skill cloudflare-pages-stale-assetsgit clone --depth 1 https://github.com/JinNing6/NoosphereWrote 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/jinning6/noosphere/cloudflare-pages-stale-assets)<a href="https://agentmods.dev/skills/jinning6/noosphere/cloudflare-pages-stale-assets"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/cloudflare-pages-stale-assets/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/jinning6/noosphere/cloudflare-pages-stale-assets"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/cloudflare-pages-stale-assets.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.00075 | $0.00565 |
| Opus 5 | $0.00037 | $0.00282 |
| Sonnet 5 | $0.00015 | $0.00113 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
cloudflare-pages-stale-assets 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 12d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cloudflare Pages Stale Assets
Use this before changing UI code again. First prove whether the failure is deployment, domain routing, edge/browser cache, or runtime JavaScript.
Workflow
- Confirm the repo state:
- Read project agent rules first.
- Check the current branch, latest commit, and dirty files.
- Identify the exact generated/static output directory used by Pages.
- Compare every live hostname:
- Fetch
https://<pages-project>.pages.dev/, the apex custom domain, andwww. - Add a cache-busting query to HTML, CSS, and JS URLs, for example
?codex_check=<timestamp>. - Record status, redirect target,
ETag,CF-Cache-Status,Age, and whether the expected new code appears.
- Fetch
- Distinguish failure layers:
- Deployment: latest commit is not in the live HTML.
- Domain routing:
pages.devis current but custom domain is stale or SSL/route-broken. - Asset cache: HTML is current but references unversioned old CSS/JS.
- Browser cache: network fetch is current but the user's browser still displays old assets.
- Runtime: assets are current but console errors prevent enhancement.
- Fix at the owning layer:
- If production branch is wrong, fix Pages branch control or redeploy the intended branch.
- If custom domain differs, fix Pages custom domain binding and DNS before editing UI.
- If stale CSS/JS is plausible, version static asset URLs in every HTML page, such as
style.css?v=<release-id>andlanguage.js?v=<release-id>. - If runtime fails, inspect console errors and fix the actual JavaScript exception.
- Verify after deploy:
- Fetch live HTML and confirm it references versioned assets.
- Fetch versioned CSS/JS and confirm they contain the expected selectors/functions.
- Use a real browser when possible to confirm DOM enhancement, not only source text.
- Tell the user whether they need a hard refresh; after versioned assets they usually should not.
Completion Standard
The latest live HTML is proven to reference the intended assets, all affected hostnames are checked or explicitly reported as unreachable, runtime errors are ruled out or fixed, and the final commit includes only task-scoped files.
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.
- 12d ago First seen · 40 lines · 75 tokens per session scan A 19d539874ff4
cloudflare-pages-stale-assets is a skill published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 5d ago), licensed Apache-2.0. It adds 75 tokens to every session and 565 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-30.
Other skills, from other repositories
gke-ai-troubleshooting-jobset-interruption
Diagnoses GKE JobSet interruptions, restarts, and preemptions for AI/ML training workloads autonomously. Use when troubleshooting JobSet restart loops, spot VM preemptions, node readiness failures, host VM issues, or coordinator worker crashes. Don't use for general GKE cluster creation, basic workload deployment, or…
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
agentcore-investigation
Investigate Bedrock AgentCore runtime sessions via CloudWatch Logs Insights — resolve session/trace IDs, query OTEL spans, filter noise, build timelines. Use when debugging AgentCore agent sessions, tracing tool calls, or analyzing latency.
network-rca
Kubernetes network root cause analysis skill powered by Kubeshark MCP. Use this skill whenever the user wants to investigate past incidents, perform retrospective traffic analysis, take or manage traffic snapshots, extract PCAPs, dissect L7 API calls from historical captures, compare traffic patterns over time, detect…
claw-admin
Claw system administration: service management, IM connections, logs, cron, and workspace diagnostics. Use when the user asks to manage claw services, connect/disconnect IM platforms, view logs, or perform system-wide operations.
optimize
Review code for efficiency and performance. Triggered by "/optimize" when user wants to identify bottlenecks or improve performance.