Borrowing it
Nothing to install: this file belongs to glassBead-tc/widescreen-research. 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/glassBead-tc/widescreen-research/main/.claude/commands/games/ulysses-protocol.mdgit clone --depth 1 https://github.com/glassBead-tc/widescreen-researchWrote 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/glassbead-tc/widescreen-research/ulysses-protocol)<a href="https://agentmods.dev/commands/glassbead-tc/widescreen-research/ulysses-protocol"><img src="https://agentmods.dev/badge/commands/glassbead-tc/widescreen-research/ulysses-protocol.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.00000 | $0.02003 |
| Opus 5 | $0.00000 | $0.01001 |
| Sonnet 5 | $0.00000 | $0.00401 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
ulysses-protocol 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 8d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ulysses Protocol
High-stakes debugging and problem-solving framework that prevents endless iteration cycles while maintaining quality through systematic phases and decision gates.
Variables
PROBLEM_STATEMENT: $ARGUMENTS ITERATION_LIMIT: $ARGUMENTS (default: 3) CONFIDENCE_THRESHOLD: $ARGUMENTS (default: 0.95) STAKES: "low" | "medium" | "high" | "critical" COMMENTS: $ARGUMENTS
Protocol Phases
Phase 1: Reconnaissance (Time-boxed: 25% of budget)
OBJECTIVE: Understand the problem space completely
=> [swarm_intelligence](../orchestration/swarm-intelligence.md): Deploy research_agent to gather all available context
=> [swarm_intelligence](../orchestration/swarm-intelligence.md): Deploy analysis_agent to map system state and dependencies
=> [time_machine](../analysis/time-machine.md): Historical context and decisions
=> [knowledge_graph](../analysis/knowledge-graph.md): Visualize relationships
GATE: Can we clearly define the problem?
- [ ] Problem statement is specific and measurable
- [ ] Root cause hypotheses are formed
- [ ] Success criteria are defined
- [ ] Risk assessment is complete
If GATE fails: Escalate or change approach
Phase 2: Strategic Planning (Time-boxed: 15% of budget)
OBJECTIVE: Design solution approach with multiple contingencies
-> [implementation_variants](../development/implementation-variants.md): Generate 3 solution approaches
-> [swarm_intelligence](../orchestration/swarm-intelligence.md): Evaluate approaches across dimensions
-> [pattern_synthesizer](../synthesis/pattern-synthesizer.md): Learn from similar problems
DECISION MATRIX:
- Implementation complexity
- Risk of unintended consequences
- Resource requirements
- Probability of success
- Rollback difficulty
GATE: Do we have a viable plan?
- [ ] Primary approach selected with high confidence
- [ ] Backup approaches identified
- [ ] Risk mitigation strategies in place
- [ ] Success metrics defined
If GATE fails: Return to reconnaissance or escalate
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.
- 8d ago First seen · 296 lines · 0 tokens per session scan A 1036eb8691b6
ulysses-protocol is a command published in the GitHub repository glassBead-tc/widescreen-research (6 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,003 tokens. 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
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…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.