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 agentmods add skills/yxhpy/openuser/hot-reloadnpx skills add yxhpy/openuser --skill hot-reloadgit clone --depth 1 https://github.com/yxhpy/openuserWrote 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/yxhpy/openuser/hot-reload)<a href="https://agentmods.dev/skills/yxhpy/openuser/hot-reload"><img src="https://agentmods.dev/badge/skills/yxhpy/openuser/hot-reload.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.02001 |
| Opus 5 | $0.00016 | $0.01001 |
| Sonnet 5 | $0.00006 | $0.00400 |
| Haiku 4.5 | $0.00003 | $0.00200 |
Grade A, and why
hot-reload scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:8000/api/v1/plugins/image-processor/reload How it starts
The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hot Reload Skill
This skill enables hot-reloading of plugins, skills, and configurations without system restart.
Trigger Conditions
This skill is triggered when:
- User requests to reload a plugin
- Plugin files are modified
- Skill files are modified
- Configuration files are changed
- User says "reload", "热更新", "刷新插件"
Behavior
When triggered, this skill will:
- Detect Changes - Identify what needs to be reloaded
- Validate Changes - Check syntax and dependencies
- Backup State - Save current state before reload
- Reload Components - Hot-reload plugins/skills/config
- Verify Reload - Test that reload was successful
- Rollback if Failed - Restore previous state if reload fails
- Update Registry - Record reload in project memory
Hot Reload Capabilities
1. Plugin Hot Reload
Reload plugins without restarting the system:
from src.core.plugin_manager import PluginManager
pm = PluginManager()
# Reload single plugin
pm.reload_plugin("image-processor")
# Reload all plugins
pm.reload_all_plugins()
# Reload with dependency resolution
pm.reload_plugin("video-editor", resolve_deps=True)
Process:
- Unload plugin (call
on_unload()hook) - Clear module cache
- Reimport plugin module
- Load plugin (call
on_load()hook) - Restore plugin state if needed
2. Skill Hot Reload
Reload Claude Code skills on-the-fly:
from src.core.skill_manager import SkillManager
sm = SkillManager()
# Reload single skill
sm.reload_skill("auto-test")
# Reload all skills
sm.reload_all_skills()
Process:
- Parse SKILL.md file
- Validate skill configuration
- Update skill registry
- Reload skill logic
3. Configuration Hot Reload
Reload configuration without restart:
from src.core.config_manager import ConfigManager
cm = ConfigManager()
# Reload configuration
cm.reload_config()
# Reload specific section
cm.reload_section("database")
# Watch for changes
cm.watch_config(auto_reload=True)
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.
- 5d ago First seen · 373 lines · 32 tokens per session scan A 5e6dd3153219
hot-reload is a skill published in the GitHub repository yxhpy/openuser (2 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 2,001 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…