Borrowing it
Nothing to install: this file belongs to ly1836/spring-ai-rag-demo. 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/ly1836/spring-ai-rag-demo/main/.cursor/commands/opsx-explore.mdgit clone --depth 1 https://github.com/ly1836/spring-ai-rag-demoWrote 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/ly1836/spring-ai-rag-demo/opsx-explore)<a href="https://agentmods.dev/commands/ly1836/spring-ai-rag-demo/opsx-explore"><img src="https://agentmods.dev/badge/commands/ly1836/spring-ai-rag-demo/opsx-explore.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.00019 | $0.01550 |
| Opus 5 | $0.00010 | $0.00775 |
| Sonnet 5 | $0.00004 | $0.00310 |
| Haiku 4.5 | $0.00002 | $0.00155 |
Grade A, and why
/opsx-explore 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.
This is a copy
86% identical to OPSX: Explore — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
IMPORTANT: Explore mode is for thinking, not implementing. You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.
This is a stance, not a workflow. There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
Input: The argument after /opsx:explore is whatever the user wants to think about. Could be:
- A vague idea: "real-time collaboration"
- A specific problem: "billing queries are getting unwieldy"
- A change name: "add-dark-mode" (to explore in context of that change)
- A comparison: "postgres vs sqlite for this"
- Nothing (just enter explore mode)
项目 context 识别
本项目是单模块 Spring Boot 应用，OpenSpec 统一在仓库根目录管理。所有 CLI 命令在根目录执行。
change 名称按业务域或能力命名（如 chat-stream-mode、billing-monthly-quota、data-access-mybatis-plus-crud），不使用模块前缀。
当话题涉及代码、架构、租户隔离、计费扣费或前端联动时：
- 读取
openspec/context/spring-ai-rag-demo.md获取项目专属架构约束 - 读取
openspec/config.yaml获取通用 OpenSpec 与编码约束
纯粹的技术探讨可跳过 context 加载。
The Stance
- Curious, not prescriptive - Ask questions that emerge naturally, don't follow a script
- Open threads, not interrogations - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
- Visual - Use ASCII diagrams liberally when they'd help clarify thinking
- Adaptive - Follow interesting threads, pivot when new information emerges
- Patient - Don't rush to conclusions, let the shape of the problem emerge
- Grounded - Explore the actual codebase when relevant, don't just theorize
What You Might Do
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 · 187 lines · 19 tokens per session scan A 3e81defdbb45
/opsx-explore is a command published in the GitHub repository ly1836/spring-ai-rag-demo (85 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 1,550 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to OPSX: Explore, differing in 54 lines, and is treated as a copy.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
clean-branches
A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.
init
A project-initialization command that scans a codebase and creates or updates CLAUDE.md files. These files give AI coding tools project and module instructions, and the command also creates navigation diagrams.
rollback
An interactive Git command for moving a branch back to an earlier commit, tag, or saved reference. It supports reset, which changes branch history, and revert, which adds new commits that undo earlier ones.
spec-research
A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.
spec-impl
An implementation command that follows an approved specification and task checklist, uses multiple analysis models, and archives the completed work. It keeps changes within the defined scope and requires external suggestions to be reviewed before use.