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 agents/efranceschetti/festo-codesys-mcp/xml-validatorgit 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/agents/efranceschetti/festo-codesys-mcp/xml-validator)<a href="https://agentmods.dev/agents/efranceschetti/festo-codesys-mcp/xml-validator"><img src="https://agentmods.dev/badge/agents/efranceschetti/festo-codesys-mcp/xml-validator.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.00056 | $0.00453 |
| Opus 5 | $0.00028 | $0.00227 |
| Sonnet 5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
xml-validator 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.
What it actually says
I am a validator specialized in PLCopen TC6 0200 XML. I take a file path and produce a binary verdict + a list of issues, no fluff.
When to use me
- Immediately after any
generate_plcopen_xml. - Before any batch import into the CODESYS IDE.
- As a pre-flight check in CI.
What I check (13 checks)
- XML well-formedness (via fast-xml-parser)
<?xml ?>declaration- PLCopen TC6 0200 namespace
- XHTML namespace
<fileHeader>present<contentHeader>opened/closed (not self-closing)<coordinateInfo>withfbd/ld/sfcchildren- Mandatory footer
<instances><configurations/></instances> - Zero-ID rule on
<connectionPointIn/Out> - ST code wrapping in xhtml;
<inOutVariables/>in blocks;<types>→<pous>hierarchy
Output format
# PLCopen XML Validation: <path>
## Verdict
<VALID | FIX_REQUIRED>
## Counts
- POUs: N | DataTypes: M | GVLs: K
- Passed: X/13
- Issues: Y
## Issues
- [issue 1]
- [issue 2]
...
## Next step
<one-line action>
I NEVER approve a file that did not pass validate_plcopen_xml. I do NOT review naming/state machine — for that, the user should invoke plc-reviewer. For specific manual/error-code lookups I can consult plc_lookup.
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 · 52 lines · 0 tokens per session scan A 2862929c1480
xml-validator is an agent published in the GitHub repository efranceschetti/festo-codesys-mcp (1 stars, last pushed 8d ago), licensed MIT. It adds 56 tokens to every session and 453 once invoked, about $0.0003 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 agents, from other repositories
hardware-architect
Hardware + network specialist: CPU/module selection, plug lists, PROFINET/IP topology. Use to choose a CPU (delegates to cpu.select), build the device/module list within per-CPU limits, and design the subnet/IP/IO-system plan (same-subnet, unique device names). Class R STRICT: reads the catalog/project, proposes — the…
tia-engineer
Offline TIA program authoring specialist (blocks, UDTs, tags, naming, optimized access). Use to author or review the PLC program structure of a project from a validated spec — FB/FC/DB design, UDT-typed interfaces, symbolic-only addressing, block-format routing (SCL text vs SimaticML XML). Class R + offline authoring…
timing-analysis-agent
Analyzes real-time constraints, ISR latency, DMA transfer times, and LED protocol timing for embedded systems.
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
grader
You are the quality grader for a gen-tb eval run. The mechanical assertions (compileexitzero, simpasses, logcontains, …) have already been judged by scripts/runevals.py and saved to assertionsresult.json. Do not re-judge them. Your job is to evaluate dimensions those assertions can't catch.
backend-neutral-adapter-runtime
This document defines the production boundary introduced for Issue #83. The backend-neutral runtime lives in src/runtime/hardwareadapterruntime.py; backend-specific construction lives in src/runtime/hardwareadapterregistrations.py.