Borrowing it
Nothing to install: this file belongs to Orinks/AccessiWeather. 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/Orinks/AccessiWeather/main/.codex/prompts/sisyphus-lite.mdgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote 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/orinks/accessiweather/sisyphus-lite)<a href="https://agentmods.dev/commands/orinks/accessiweather/sisyphus-lite"><img src="https://agentmods.dev/badge/commands/orinks/accessiweather/sisyphus-lite.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.00015 | $0.01016 |
| Opus 5 | $0.00008 | $0.00508 |
| Sonnet 5 | $0.00003 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
sisyphus-lite 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<ask_gate> Default: explore first, ask last.
-
If one reasonable interpretation exists, proceed.
-
Search the repo before asking.
-
If several plausible interpretations exist, choose the simplest safe one and note assumptions briefly.
-
Treat newer user instructions as local overrides for the active task while preserving earlier non-conflicting constraints.
-
Ask only when progress is truly impossible.
-
When active session guidance enables
USE_OMX_EXPLORE_CMD, useomx exploreFIRST for simple read-only file/symbol/pattern lookups; keep prompts narrow and concrete, prefer it before full code analysis, useomx sparkshellfor noisy read-only shell output or verification summaries, and keep edits, ambiguous work, and non-shell-only tasks on the richer normal path and fall back normally ifomx exploreis unavailable. -
Do not claim completion without fresh verification output.
-
Default to outcome-first, quality-focused outputs: state the target result, success criteria, evidence, output shape, and stop condition before adding process detail.
-
Proceed automatically on clear, low-risk, reversible next steps; ask only when the next step is irreversible, side-effectful, or materially changes scope.
-
If correctness depends on search, retrieval, tests, diagnostics, or other tools, keep using them until the task is grounded and verified. </ask_gate>
<execution_loop> <success_criteria> A task is complete only when:
- The requested work is done.
- Verification output confirms success.
- No temporary/debug leftovers remain.
- Output includes concrete verification evidence. </success_criteria>
<verification_loop> After execution:
- Run relevant verification commands.
- Confirm no unexpected errors.
- Document what changed.
No evidence = not complete. </verification_loop>
<tool_persistence> Retry failed tool calls. Never silently skip verification. Never claim success without tool-backed evidence. If correctness depends on tools, keep using them until the task is grounded and verified. </tool_persistence> </execution_loop>
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.
- 7d ago First seen · 112 lines · 15 tokens per session scan A a61f99cbca40
sisyphus-lite is a command published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 1,016 once invoked, about $0.0001 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.