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/commands/cycle-test.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/commands/efranceschetti/festo-codesys-mcp/cycle-test)<a href="https://agentmods.dev/commands/efranceschetti/festo-codesys-mcp/cycle-test"><img src="https://agentmods.dev/badge/commands/efranceschetti/festo-codesys-mcp/cycle-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/efranceschetti/festo-codesys-mcp/cycle-test"><img src="https://agentmods.dev/badge/commands/efranceschetti/festo-codesys-mcp/cycle-test.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00521 |
| Opus 5.5 | $0.00014 | $0.00208 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade C, and why
cycle-test scanned grade C 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
7. **Cleanup** — `Bash` run `rm -rf tmp-cycle-test` (Linux/Mac) or `Remove-Item -Recurse -Force tmp-cycle-test` (Windows). What it actually says
Run an MCP cycle-test exercising the main offline pipeline (6 of the 18 core tools). Do NOT commit anything at the end.
Sequential steps:
- Base conventions — call
plc_lookupwithaction=list_standardto list Hungarian prefixes + state machine ranges. Summarize in 3 lines. - Library inventory — call
plc_librarywithaction=listto confirm the 38 FBs are accessible. Report the count per category. - Create a test FB — call
create_function_blockwith:- name:
FB_CycleTestCylinder - description: "Pneumatic cylinder with 5s timeout — generated by /cycle-test"
- inputs:
bExtend BOOL,tTimeout TIME - outputs:
bExtended BOOL,bDone BOOL,bErr BOOL,nErrId DINT - write to
tmp-cycle-test/FB_CycleTestCylinder.st
- name:
- Validate ST —
Readthe generated .st file and callplc_validateaction=naming with its code. Expect zero naming violations. - Generate PLCopen XML — call
generate_plcopen_xmlontmp-cycle-test/producingtmp-cycle-test/cycle-test.xml. - Validate XML — call
validate_plcopen_xmlon the generated file. Expect all 13 checks to pass. - Cleanup —
Bashrunrm -rf tmp-cycle-test(Linux/Mac) orRemove-Item -Recurse -Force tmp-cycle-test(Windows). - Final report — a markdown table: tool, status, note.
If any step fails, stop immediately, show the full error, and suggest a root cause.
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.
- 1mo ago First seen · 25 lines · 35 tokens per session scan C 051c4b010e27
cycle-test is a command published in the GitHub repository efranceschetti/festo-codesys-mcp (2 stars, last pushed 21d ago), licensed MIT. It adds 35 tokens to every session and 521 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.