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/daily-warmup.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/daily-warmup)<a href="https://agentmods.dev/commands/efranceschetti/festo-codesys-mcp/daily-warmup"><img src="https://agentmods.dev/badge/commands/efranceschetti/festo-codesys-mcp/daily-warmup/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/daily-warmup"><img src="https://agentmods.dev/badge/commands/efranceschetti/festo-codesys-mcp/daily-warmup.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.00030 | $0.00313 |
| Opus 5.5 | $0.00012 | $0.00125 |
| Sonnet 5.5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
daily-warmup 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 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.
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
Pre-work routine. Run in order; stop at the first error and report.
Sequence:
- Local status —
git status --short. If there are pending changes, WARN the user but continue. - Sync with remote —
git fetch origin, then showgit log HEAD..origin/main --onelineto see what is new. Do NOT pull automatically — ask whether to integrate. - Check the lockfile —
git diff --name-only HEAD..origin/main -- package-lock.json(after the fetch above). If it changed on the remote, runnpm ci. - Build/test/lint cycle — sequential:
npm run buildnpm testnpm run lintStop at the first failure.
- Latest commits —
git log --oneline -10. - Open PRs —
gh pr list --state open(ifghis available; fail silently otherwise). - Final summary — one line:
✓ ready to work | branch=<X> | <Y> commits ahead/behind | tests=<N>/<N>.
NEVER commit, push, or merge automatically in this routine.
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 · 23 lines · 30 tokens per session scan A 1d0400697492
daily-warmup is a command published in the GitHub repository efranceschetti/festo-codesys-mcp (2 stars, last pushed 21d ago), licensed MIT. It adds 30 tokens to every session and 313 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
implement-feature
Implement an approved feature plan with benefit-based placement, TDD, revision-bound evidence, and PR-ready output.
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.
verify
Run verification commands and confirm output before making success claims. Use before committing, creating PRs, or claiming work is complete. Evidence before assertions, ALWAYS.