How do I install the Build Modscan skill?

Run npx skillmds@latest add studioxvii/build-modscan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build Modscan safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build Modscan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build Modscan free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Build Modscan?

studioxvii (@studioxvii) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build Modscan by studioxvii — Agent Skill

Name: Build Modscan
Author: studioxvii

Build Modscan

Build deterministic read-only BETA ModScan setup, poll-plan, point-map, and protocol test-message artifacts. Use when the user asks for ModScan files, a ModScan read plan, or ModScan probe/final setup.

studioxvii 7ccaad0 5 files · 6.4 KB Updated Sep 17, 2026

File contents

Build ModScan (BETA)

Generate documented setup files. This target remains BETA; generation does not verify the user's installed application or native polling behavior.

Follow ../../references/interaction-contract.md.

Process

Read references/options.md before using options or making a version claim.
Infer ModScan32 or ModScan64 from the request or available installation; ask once only when the target genuinely affects the output and cannot be discovered.
Require a canonical map, read plan, and probe or final mode.
Run python3 <skill-dir>/scripts/run.py --map <map.json> --plan <read-plan.json> --mode <mode> --output <directory>.
Inspect the setup manifest and generated CSV files.
Configure ModScan from the plan when available; these CSVs are operator-entry instructions, not native import files. Otherwise report native verification as unavailable and use the fallback only for one reviewed request.
Use the generated Point Address column for the tested ModScan UI; raw protocol messages retain zero-based offsets. Follow the generated README and references/native-verification.md for the version-specific mapping.

Output files

modscan/read-plan.csv - The bounded read blocks to enter in ModScan.
modscan/point-map.csv - The names and meanings of the returned registers.
modscan/test-message-plan.csv - Optional protocol test messages for verification.
modscan/README.md - Start here for setup instructions.
modscan/pymodbus-read-once.py - Optional cross-platform FC01-04 fallback. It requires one compiled request, endpoint, port, and matching unit ID.
The JSON manifest and result files - Normally ignore these. They prove which map and plan produced the CSV files and record any holds.

Completion requires a generated or held status with visible native-verification state.

Windows lab verification

For native application checks, follow references/native-verification.md. Keep receipts in a local diagnostic directory, separate from the user deliverables.

Stop

Stop without a canonical map, read plan, and probe or final mode.
Never claim native verification when it was not run.
Do not invent undocumented ModScan configuration formats.

Handoff

No read plan exists: suggest plan-reads.
The user needs several target formats: suggest build-tool-pack.

Preserve documented ModScan files. Never claim native verification when it was not run.

---name: build-modscandescription: Build deterministic read-only BETA ModScan setup, poll-plan, point-map, and protocol test-message artifacts. Use when the user asks for ModScan files, a ModScan read plan, or ModScan probe/final setup.license: Apache-2.0---# Build ModScan (BETA)Generate documented setup files. This target remains BETA; generation does notverify the user's installed application or native polling behavior.Follow `../../references/interaction-contract.md`.## Process1. Read `references/options.md` before using options or making a version claim.2. Infer ModScan32 or ModScan64 from the request or available installation; ask once only when the target genuinely affects the output and cannot be discovered.3. Require a canonical map, read plan, and `probe` or `final` mode.4. Run `python3 <skill-dir>/scripts/run.py --map <map.json> --plan <read-plan.json> --mode <mode> --output <directory>`.5. Inspect the setup manifest and generated CSV files.6. Configure ModScan from the plan when available; these CSVs are operator-entry instructions, not native import files. Otherwise report native verification as unavailable and use the fallback only for one reviewed request.7. Use the generated Point Address column for the tested ModScan UI; raw protocol messages retain zero-based offsets. Follow the generated README and `references/native-verification.md` for the version-specific mapping.## Output files- `modscan/read-plan.csv` - The bounded read blocks to enter in ModScan.- `modscan/point-map.csv` - The names and meanings of the returned registers.- `modscan/test-message-plan.csv` - Optional protocol test messages for verification.- `modscan/README.md` - Start here for setup instructions.- `modscan/pymodbus-read-once.py` - Optional cross-platform FC01-04 fallback. It requires one compiled request, endpoint, port, and matching unit ID.- The JSON manifest and result files - Normally ignore these. They prove which map and plan produced the CSV files and record any holds.Completion requires a generated or held status with visible native-verification state.## Windows lab verificationFor native application checks, follow `references/native-verification.md`.Keep receipts in a local diagnostic directory, separate from the user deliverables.## Stop- Stop without a canonical map, read plan, and probe or final mode.- Never claim native verification when it was not run.- Do not invent undocumented ModScan configuration formats.## Handoff- No read plan exists: suggest `plan-reads`.- The user needs several target formats: suggest `build-tool-pack`.Preserve documented ModScan files. Never claim native verification when it was not run.

Frequently asked questions