Borrowing it
Nothing to install: this file belongs to efranceschetti/festo-codesys-mcp. 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/efranceschetti/festo-codesys-mcp/main/.claude/skills/plcopen-xml/SKILL.mdgit clone --depth 1 https://github.com/efranceschetti/festo-codesys-mcpWrote 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/efranceschetti/festo-codesys-mcp/plcopen-xml)<a href="https://agentmods.dev/skills/efranceschetti/festo-codesys-mcp/plcopen-xml"><img src="https://agentmods.dev/badge/skills/efranceschetti/festo-codesys-mcp/plcopen-xml.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.1 | $0.00063 | $0.00371 |
| Opus 5 | $0.00032 | $0.00186 |
| Sonnet 5 | $0.00013 | $0.00074 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade B, and why
plcopen-xml scanned grade B 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 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
Any failure -> fix sources, regenerate, restart the chain. NEVER tell the user the file is import-ready before all three pass. What it actually says
PLCopen XML Pipeline
PLCopen XML is the #1 hallucination risk in this project. Never hand-write it; never trust it unvalidated.
1. Ground truth first
plc_knowledgeaction=topicground-truth(anti-hallucination rules), thenxml-rules.- Skip only if already loaded this session.
2. Generate — never hand-write
generate_plcopen_xmlwith the .st source directory. Fix the .st sources and regenerate rather than editing XML by hand.
3. Validation chain (all three, in order)
validate_plcopen_xml— fast 13-rule sanity gate.validate_plcopen_xsd— official TC6 v2.00 schema (needs python venv with lxml).validate_plcopen_semantic— confirms no variables/initializers silently dropped vs the .st sources.
Any failure -> fix sources, regenerate, restart the chain. NEVER tell the user the file is import-ready before all three pass.
4. Delegate the final check
Before the user imports into the CODESYS IDE, delegate to the xml-validator subagent (fast, cheap) for the copy-pasteable verdict report.
5. Import checklist for the user
CODESYS -> File -> Import PLCopen XML -> resolve namespace conflicts -> Build -> Generate Code (expect 0 errors).
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 · 29 lines · 63 tokens per session scan B ee9b2ac92885
plcopen-xml is a skill published in the GitHub repository efranceschetti/festo-codesys-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 371 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
codesys
Comprehensive operational skill specification for Anthropic Claude to automate, script, troubleshoot, and optimize CODESYS V3.5, IEC 61131-3 Structured Text (ST), ScriptEngine Python automation, EtherCAT/PROFINET, and OPC UA.
tia.init
Initialize or update the current project's AGENTS.md with the TIA harness operating guide. USE WHEN the user asks to "init / bootstrap / set up the TIA harness", "add the harness guidance to AGENTS.md", or "update the TIA harness section / refresh the harness guide in this project". Idempotent: injects the guide…
cpu.select
Recommend a Siemens S7-1500/S7-1200 CPU family + variant + order number (MLFB) from an engineering need (I/O count, scan/performance, memory, communication ports, safety, redundancy, motion). USE when the user asks "which CPU / PLC should I use", gives selection criteria instead of a model, or needs a typeIdentifier…
spec.validate
Validate a TIA project-spec against the JSON Schema AND the deterministic cross-field engineering rules (same-subnet, unique names, OrderNumber: /V format, module limits, language-by-family, and the G5 safety rule). USE when the user provides or edits a project-spec, asks to "validate / check / lint my spec", or…
tia.handoff
Prepare a human-approval envelope for a GATED operation — download / CPU-STOP (G3), go-online (G4), network scan (G7), master-secret/UMAC (G6), safety/F (G5). USE WHEN the user wants to "download / deploy / go online / commission", or after tia.verify is clean and the next step touches the physical controller, the…
tia.scaffold
Build a TIA project FROM a validated project-spec — the create-from-spec pipeline: subnets → devices → modules → network/IP → tag tables/tags → block shells → protection setup → compile. USE WHEN the user says "scaffold / build / create the project from this spec", "generate the TIA project", after spec.validate +…