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/ipsymconnpx skills add Schimmilab/ipsymcon-mcp-server --skill ipsymcongit 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/ipsymcon)<a href="https://agentmods.dev/skills/schimmilab/ipsymcon-mcp-server/ipsymcon"><img src="https://agentmods.dev/badge/skills/schimmilab/ipsymcon-mcp-server/ipsymcon.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.00049 | $0.01679 |
| Opus 5 | $0.00024 | $0.00839 |
| Sonnet 5 | $0.00010 | $0.00336 |
| Haiku 4.5 | $0.00005 | $0.00168 |
Grade A, and why
ipsymcon 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IP-Symcon development
This skill turns you into a careful developer inside a live IP-Symcon home automation.
You don't just switch devices — you read the system, build PHP scripts, create variables
and events, and grow the automation. The ipsymcon MCP is your hands; this skill is the
playbook for using them well and safely.
- How to carry out a change (step-by-step workflows, plan & report templates, pitfalls): references/workflow.md.
ips_callfunction cheat-sheet (signatures + recipes for event triggers, profiles, instances, rename/move/delete): references/ips-functions.md.
The one rule that matters: plan before you touch
IP-Symcon runs a real house — heating, blinds, sockets, sensors. A wrong write can have physical consequences. So the workflow is read → plan → approve → execute → report, never "change first, explain later". The user explicitly wants to see what will change, from where to where, before anything happens. There is also an IP-Symcon backup as a safety net, but the plan is the primary guardrail.
- Start in plan mode (
EnterPlanMode). Reading is fine — explore freely. - Resolve and read the current state of everything you intend to change. IDs are opaque integers; never guess them, always resolve from names/tree.
- Assemble a plan naming every change as a concrete operation with a clear before → after (template in workflow.md).
- Present the plan via
ExitPlanModeand stop. Do not call a single write tool yet. - Only after approval, execute the writes in order, capturing each result.
- Report exactly what changed — every operation performed, with IDs and before/after. If a step fails, stop and report; don't push on.
If you ever find yourself about to call any write/dev tool (anything in the second table below) before the user has seen and approved a plan — stop. That's the failure mode this skill exists to prevent.
What ships with it
2 files 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 · 106 lines · 49 tokens per session scan A 00030278d4bc
ipsymcon is a skill published in the GitHub repository Schimmilab/ipsymcon-mcp-server (0 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,679 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.
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.
smartest-tv
Control a smart TV or open streaming content in the browser. Play Netflix episodes/movies, YouTube videos, Spotify music — on TV or in browser (--tv browser). Also handles volume, power, notifications, history, 'continue watching', scenes, recommendations, cast URLs, queue, and multi-TV management. Triggers on…
streamdeck-designer
Design, theme, and author complete Stream Deck layouts for the user's hardware using the streamdeck-mcp tools. Use whenever the user wants a custom Stream Deck setup, asks for a themed deck (e.g. "hello-kitty Twitch deck", "retrowave music controls", "a dev deck for this repo"), wants buttons or dials configured for…