Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问clear审计异常

codex-claude-cursor-loopCodex Claude Cursor loop 搜索

Agent Skill

codex-claude-cursor-loop 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

499

周安装

20

GitHub Stars

836

下载量

162
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:codex-claude-cursor-loop(Codex Claude Cursor loop 搜索)
来源仓库:https://github.com/bear2u/my-skills
仓库路径:skills/codex-claude-cursor-loop
安装命令:
npx skills add https://github.com/bear2u/my-skills --skill codex-claude-cursor-loop
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/bear2u/my-skills --skill codex-claude-cursor-loop

简介

codex-claude-cursor-loop 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 它实现三阶段工程验证循环:Claude 负责架构规划,Codex 负责逻辑与安全审查,Cursor 负责代码实施。
  • 通过顺序验证机制确保每次修改都经过多层校验,提升代码质量和安全性。
  • 安装命令为 npx skills add https://github.com/bear2u/my-skills --skill codex-claude-cursor-loop,需确认各组件兼容性。
  • 使用前建议核实各宿主平台间的协作机制和权限边界,避免执行冲突。

SKILL.md

Codex-Claude-Cursor Engineering Loop Skill

Core Workflow Philosophy

This skill implements a 3-way sequential validation engineering loop:

  • Claude Code: Architecture and planning, final review
  • Codex: Plan validation (logic/security), code review (bugs/performance)
  • Cursor Agent: Code implementation and execution
  • Sequential Validation: Claude plans → Codex validates → Cursor implements → Codex reviews → Claude final check → repeat

Phase 1: Planning with Claude Code

  1. Start by creating a detailed plan for the task
  2. Break down the implementation into clear steps
  3. Document assumptions and potential issues
  4. Output the plan in a structured format

Phase 2: Plan Validation with Codex

  1. Ask user (via AskUserQuestion):

- Model: gpt-5 or gpt-5-codex - Reasoning effort: low, medium, or high

  1. Send the plan to Codex for validation:
   echo "Review this implementation plan and identify any issues:
   [Claude's plan here]

   Check for:
   - Logic errors
   - Missing edge cases
   - Architecture flaws
   - Security concerns" | codex exec -m <model> --config model_reasoning_effort="<effort>" --sandbox read-only
  1. Capture Codex's feedback and summarize to user

Phase 3: Plan Refinement Loop

If Codex finds issues in the plan:

  1. Summarize Codex's concerns to the user
  2. Refine the plan based on feedback
  3. Ask user (via AskUserQuestion): "Should I revise the plan and re-validate, or proceed with implementation?"
  4. Repeat Phase 2 if needed until plan is solid

Phase 4: Implementation with Cursor Agent

Once the plan is validated by Codex:

Session Management

  1. Ask user (via AskUserQuestion): "Do you want to start a new Cursor session or resume an existing one?"

- New session: Start fresh - Resume session: Continue previous work

  1. If resuming:
   # List available sessions
   cursor-agent ls

   # Let user select session ID
   # Store session ID for subsequent calls
  1. Ask user (via AskUserQuestion): Which Cursor model to use (e.g., composer-1, claude-3.5-sonnet, gpt-4o)

Implementation

  1. Send the validated plan to Cursor Agent:

For new session:

   cursor-agent --model "<model-name>" -p --force "Implement this plan:
   [Validated plan here]

   Please implement the code following these specifications exactly."

For resumed session:

   cursor-agent --resume="<session-id>" -p --force "Continue implementation:
   [Validated plan here]"
  1. IMPORTANT: Store the session ID from the output for all subsequent Cursor calls
  2. Capture what was implemented and which files were modified

Phase 5: Codex Code Review

After Cursor implements:

  1. Send Cursor's implementation to Codex for code review:
   echo "Review this implementation for:
   - Bugs and logic errors
   - Performance issues
   - Security vulnerabilities
   - Best practices violations
   - Code quality concerns

   Files modified: [list of files]
   Implementation summary: [what Cursor did]" | codex exec --sandbox read-only
  1. Capture Codex's code review feedback
  2. Summarize findings to user

Phase 6: Claude's Final Review

After Codex code review:

  1. Claude reads the implemented code using Read tool
  2. Claude analyzes both:

- Codex's review findings - The actual implementation

  1. Claude provides final assessment:

- Verify if it matches the original plan - Confirm Codex's findings are valid - Identify any additional concerns - Make final architectural decisions

  1. Summarize overall quality and readiness

Phase 7: Iterative Improvement Loop

If issues are found (by Codex or Claude):

  1. Claude creates a detailed fix plan based on:

- Codex's code review findings - Claude's final review insights

  1. Send the fix plan to Cursor Agent using the same session:
   # IMPORTANT: Use --resume with the stored session ID
   cursor-agent --resume="<session-id>" -p --force "Fix these issues:
   [Detailed fix plan]

   Issues from Codex: [list]
   Issues from Claude: [list]"
  1. After Cursor fixes, repeat from Phase 5 (Codex code review)
  2. Continue the loop until all validations pass
  3. Note:

- Use same Codex model for consistency - Always use the same Cursor session ID to maintain context - Session maintains full history of changes

Recovery When Issues Are Found

When Codex finds plan issues (Phase 2):

  1. Claude analyzes Codex's concerns
  2. Refines the plan addressing all issues
  3. Re-submits to Codex for validation
  4. Repeats until Codex approves

When Codex finds code issues (Phase 5):

  1. Claude reviews Codex's findings
  2. Creates detailed fix plan
  3. Sends to Cursor for fixes
  4. After Cursor fixes, back to Codex review
  5. Repeats until Codex approves

When Claude finds issues (Phase 6):

  1. Claude creates comprehensive fix plan
  2. Sends to Cursor for implementation
  3. After fixes, Codex reviews again
  4. Claude does final check
  5. Repeats until Claude approves

Best Practices

  • Always validate plans with Codex before implementation
  • Never skip Codex code review after Cursor implements
  • Never skip Claude's final review for architectural oversight
  • Maintain clear handoff between all three AIs
  • Document who did what for context
  • Use same models throughout (same Codex model, same Cursor model)
  • Session Management:

- Always use --resume with same session ID for iterative fixes - Store session ID at the start and reuse throughout - Use cursor-agent ls to find previous sessions - Only start new session when beginning completely new feature

Command Reference

PhaseWhoCommand PatternPurpose
1. PlanClaudeTodoWrite, Read, analysis toolsClaude creates detailed plan
2. Validate planCodex`echo "plan" \codex exec -m <model> --config model_reasoning_effort="<effort>" --sandbox read-only`Codex validates logic/security
3. RefineClaudeAnalyze Codex feedback, update planClaude fixes plan issues
4. Session setupClaude + UserAsk new/resume, cursor-agent ls if neededSetup or resume Cursor session
5. ImplementCursorcursor-agent --model "<model>" -p --force "prompt" OR cursor-agent --resume="<id>" -p --force "prompt"Cursor implements validated plan
6. Review codeCodex`echo "review" \codex exec --sandbox read-only`Codex reviews for bugs/performance
7. Final reviewClaudeRead tool, analysisClaude final architectural check
8. Fix planClaudeCreate detailed fix planClaude plans fixes from all feedback
9. Apply fixesCursorcursor-agent --resume="<id>" -p --force "fixes"Cursor implements fixes in same session
10. Re-reviewCodex + ClaudeRepeat phases 6-7Validate fixes until perfect

Error Handling

  1. Monitor Cursor Agent output for errors
  2. Summarize Cursor's implementation results and Claude's review
  3. Ask for user direction via AskUserQuestion if:

- Significant architectural changes needed - Multiple files will be affected - Breaking changes are required

  1. When issues appear, Claude creates a detailed fix plan before sending to Cursor

The Perfect Loop

1. Plan (Claude)
   ↓
2. Validate Plan (Codex) → if issues → refine plan → repeat
   ↓
3. Implement (Cursor)
   ↓
4. Code Review (Codex) → captures bugs/performance issues
   ↓
5. Final Review (Claude) → architectural check
   ↓
6. Issues found? → Fix Plan (Claude) → Implement Fixes (Cursor) → back to step 4
   ↓
7. All passed? → Done! ✅

This creates a triple-validation, self-correcting, high-quality engineering system where:

  • Claude: All planning, architecture, and final oversight
  • Codex: All validation (plan logic + code quality)
  • Cursor Agent: All implementation and coding

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

27.54%
按下载量换算45

OpenCode

22.33%
按下载量换算36

Cursor

19.68%
按下载量换算32

Antigravity

11.49%
按下载量换算19

Gemini CLI

7.74%
按下载量换算13

windsurf

3.49%
按下载量换算6

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。

来源信息

继续浏览同类 Skills