What is hot-patch-static-assets?

A procedure for changing frontend files served by a running web server when restarting that server is not possible or desirable. Frontend assets are files such as JavaScript, HTML, CSS, and images that a browser loads.

Use it to locate the real static-file directory, rebuild frontend assets, and apply the new files to a long-running server without restarting it.

It addresses the case where local edits do not appear because the server is serving files from a different installed or built location. It identifies that location and replaces the served files after rebuilding.

How ziya-ai/ziya configures Claude Code and Codex

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/ziya-ai/ziya/main/.agents/skills/hot-patch-static-assets/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/ziya-ai/ziya

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ziya-ai/ziya/hot-patch-static-assets/github.svg)](https://agentmods.dev/skills/ziya-ai/ziya/hot-patch-static-assets)

Your own site

<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/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 636 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00015	$0.00254
Sonnet 5.5	$0.00008	$0.00127
Haiku 4.5	$0.00004	$0.00064

Measured 2mo ago against content hash adea8127a3a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.agents/skills/hot-patch-static-assets/SKILL.md · 65 lines

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 install layouts — 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
grep confirms your code is in the new bundle, but runtime doesn't reflect it
Project was pip install'd (not pip install -e) or assets are vendored into a package
Two copies of templates/ or static/ 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

Read the full file on GitHub · 65 lines

Changes

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.

2mo ago First seen · 65 lines · 38 tokens per session scan A adea8127a3a9

Subscribe to this mod's changes

hot-patch-static-assets is a skill published in the GitHub repository ziya-ai/ziya (42 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 636 once invoked, about $0.0002 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.

Frontend ai ai-assistant ai-client ai-frontend architecture bedrock

hot-patch-static-assets next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
hot-patch-static-assetsziya-ai/ziya	Skill	42	3d ago	MIT	A	38	Claude Code, Codex
apply-perspective-drawingjeffreytse/grimoire-core	Skill	6	21d ago	MIT	A	25	Claude Code
aws-genai-ml-architectawslabs/hcls-agent-skills	Skill	72	1mo ago	MIT-0	A	189	Claude Code, Codex
ctx:architectshakestzd/contextune	Skill	5	10mo ago	MIT	A	62	Claude Code
github-multi-repoairmcp-com/mcp-standards	Skill	3	11mo ago	MIT	A	21	Claude Code
sparc-methodologyairmcp-com/mcp-standards	Skill	3	11mo ago	MIT	A	29	Claude Code
add-resendnanocoai/nanoclaw	Skill	31k	yesterday	MIT	A	16	Claude Code

ziya: Skill for Claude Code