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/schimmilab/ipsymcon-mcp-server/ips-refactornpx skills add Schimmilab/ipsymcon-mcp-server --skill ips-refactorgit clone --depth 1 https://github.com/Schimmilab/ipsymcon-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/schimmilab/ipsymcon-mcp-server/ips-refactor)<a href="https://agentmods.dev/skills/schimmilab/ipsymcon-mcp-server/ips-refactor"><img src="https://agentmods.dev/badge/skills/schimmilab/ipsymcon-mcp-server/ips-refactor.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.00046 | $0.00527 |
| Opus 5 | $0.00023 | $0.00264 |
| Sonnet 5 | $0.00009 | $0.00105 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
ips-refactor 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 3d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IP-Symcon — refactoring
Restructure what works so it stays understandable, without changing behaviour. The measure of success is unusual: nothing may change except the structure. Every value, every schedule, every automation behaves exactly as before.
REQUIRED BACKGROUND: the ipsymcon skill (plan-before-you-touch, ID resolution) and the
three-vector dependency scan from ips-cleanup — a rename or move breaks the same
references a delete does.
Not this skill: removing dead objects → ips-cleanup. Moving to another instance →
ips-migration. Building something new → ips-automation.
Full procedure: references/workflow.md.
The rule that defines refactoring
Behaviour is frozen; only structure moves. Before touching anything, snapshot the values
that must stay identical (ips_snapshot_variables). After the change, diff them
(ips_diff_variables). A refactoring that changes a value is a bug, not an improvement.
What counts as refactoring here
| Smell | Move |
|---|---|
| Two variables holding the same value, only one archived | Consolidate onto the archived one, repoint references, retire the other |
Unnamed Object links |
Name them after what they point at |
| Dozens of links loose in one category | Group into sub-categories, set positions |
| Threshold/time hardcoded in a script | Extract into a variable with profile + action |
| Scripts and helpers visible in the visualisation | Hide the machinery, keep only what is operated or read |
| Three parallel integrations of the same device | Decide which is productive — then this becomes a ips-cleanup job for the others |
Never
- Never rename or move before the dependency scan. Scripts reference IDs, but also names
via
IPS_GetObjectIDByName— a rename can break code that a pure ID search will not find. - Never resolve a duplicate by deleting first. Repoint every reference, let it run, remove afterwards.
- Never refactor and fix in the same step. If you find something broken mid-refactor, note it and finish the structural change first — otherwise the diff no longer proves anything.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 47 lines · 46 tokens per session scan A 1deb4a1a6571
ips-refactor is a skill published in the GitHub repository Schimmilab/ipsymcon-mcp-server (0 stars, last pushed 6d ago), licensed MIT. It adds 46 tokens to every session and 527 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-31.
Other skills, from other repositories
home-assistant-rest
Control and query Home Assistant through the connector's callservice tool — REST API patterns, common domains, how to find entities before acting.
devices-mcp-home
Live inventory of the user's smart home on this devices-mcp installation — cameras, Hue lights, Tapo P115 plugs, Netatmo weather, Ring, Nest Protect, Shelly sensors, and robots. Use when the user asks what devices they have, what's online, or wants a status summary before controlling hardware.
bump-dependency
Bumps a Python package dependency across Home Assistant Core integrations, regenerates core requirement files, runs verification tests and prek lint, and prepares a pull request with proper release/compare links.
bat-story-eval
Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.
unifi-protect
How to manage UniFi Protect cameras and NVR — view cameras, smart detections, Find Anything detection search, recordings, snapshots, lights, sensors, Known Faces, license plates, and the Alarm Manager. Use this skill when the user mentions UniFi cameras, security cameras, NVR, recordings, motion detection, person…
network-health-check
Run a UniFi network health check — diagnose device status, connectivity issues, firmware updates, and system health. Use when asked to check network health, find what's down, diagnose connectivity issues, or get a network status summary.