Borrowing it
Nothing to install: this file belongs to ziya-ai/ziya. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ziya-ai/ziya/main/.agents/skills/hot-patch-static-assets/SKILL.mdgit clone --depth 1 https://github.com/ziya-ai/ziyaWrote 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/ziya-ai/ziya/hot-patch-static-assets)<a href="https://agentmods.dev/skills/ziya-ai/ziya/hot-patch-static-assets"><img src="https://agentmods.dev/badge/skills/ziya-ai/ziya/hot-patch-static-assets.svg" alt="Measured on agentmods" 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.00038 | $0.00636 |
| Opus 5 | $0.00019 | $0.00318 |
| Sonnet 5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
hot-patch-static-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 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hot-Patching a Running Server's Static Assets
When to use
You edited frontend/static code (JS bundle, HTML template, CSS, image), rebuilt it, and your changes don't appear at runtime — yet you can't restart the server (or restarting is expensive/disruptive).
Core insight
A running server's process memory (Python/Node code) is frozen until restart, but static files it serves from disk can be swapped live. Each new request re-reads them.
Procedure
-
Identify the actual serving path. Don't assume the server reads from your repo. Find where the running process loads assets from:
lsof -p <pid>to see open files- Check for installed-package paths (
site-packages/,node_modules/,dist/) - Look for non-editable
pip installlayouts — source edits won't propagate - Grep server logs/config for template or static directories
- Read the server's static-mount / template-loader code
-
Build the asset locally (
npm run build,craco build, etc.) into the project's normal output directory. -
Copy build output to the actual serve path — even if it's outside your usual writable scope (e.g.
~/.pyenv/.../site-packages/...). Try the write; many sandboxes allow it. -
Trigger a fresh request. No restart needed for static files — the next request reads the new bytes off disk.
-
Verify with the rendering/test tool, not by inspecting the build output. Caches (browser, service worker, CDN) can mask success; if results look stale, hard-reload or bust the cache.
Red flags that you're hitting this problem
- "I rebuilt but the behavior is identical"
- The error message is byte-identical to before your fix
grepconfirms your code is in the new bundle, but runtime doesn't reflect it- Project was
pip install'd (notpip install -e) or assets are vendored into a package - Two copies of
templates/orstatic/exist on disk
Doesn't work when
- The change is in server code (Python/Node) — needs process restart
- Assets are bundled into memory at server startup (read-once)
- A reverse proxy/CDN caches aggressively without a bust mechanism
- The server uses a hashed manifest and your new bundle has a different hash that nothing references
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 · 65 lines · 38 tokens per session scan A adea8127a3a9
hot-patch-static-assets is a skill published in the GitHub repository ziya-ai/ziya (38 stars, last pushed 6d ago), licensed MIT. It adds 38 tokens to every session and 636 once invoked, about $0.0002 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
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
ui-design-executor
Use this as UIDesigner's default execution skill. It contains the baseline design, accessibility, HTML, runtime-safety, responsive, taste, and verification rules needed by ordinary UI work. Do not load the separate system, control, taste, color, renderer, or craft skills merely to repeat these baseline rules.
ui-design-source
Use this skill when the user provides Figma material, design-export files, screenshots of design tools, PDFs, JSON, existing HTML, or asks for design-to-HTML/code fidelity. It adapts OpenDesign/Figma handoff discipline for UIDesigner without requiring a live Figma runtime.
ui-design-system
Use this skill when creating, extending, or auditing a product UI system. It adapts Better Design-style design-system discipline without requiring an external runtime package.
seo-cwv
Measure Core Web Vitals with the free PageSpeed Insights API. Field data (CrUX, real users) is reported as Measured; lab (Lighthouse synthetic) as Estimated.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…