Skip to content
Back to search

ultracode-skill

Codex-first Ultracode skill for dynamic coding workflows

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/pablonax-ultracode-skill/badge.svg)](/listings/pablonax-ultracode-skill)

HTML

<a href="/listings/pablonax-ultracode-skill"><img src="/api/listings/pablonax-ultracode-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

The installable skill folder is `ultracode/`.

Codex

mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
cp -R ultracode "${CODEX_HOME:-$HOME/.codex}/skills/"

Restart Codex after installing.

Claude Code

mkdir -p "$HOME/.claude/skills"
cp -R ultracode "$HOME/.claude/skills/"

Antigravity

Workspace install:

mkdir -p .agents/skills
cp -R /path/to/ultracode .agents/skills/

User install:

mkdir -p "$HOME/.gemini/antigravity/skills"
cp -R ultracode "$HOME/.gemini/antigravity/skills/"

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 161 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Ultracode Skill
  2. [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
  3. [![Codex](https://img.shields.io/badge/Codex-skill-10A37F)](https://developers.openai.com/api/docs/guides/tools-skills)
  4. [![Claude Code](https://img.shields.io/badge/Claude%20Code-compatible-D97706)](https://code.claude.com/docs/en/skills)
  5. [![Antigravity](https://img.shields.io/badge/Antigravity-compatible-4285F4)](https://antigravity.google/docs/skills)
  6. [![GitHub stars](https://img.shields.io/github/stars/PabloNAX/ultracode-skill?style=social)](https://github.com/PabloNAX/ultracode-skill/stargazers)
  7. Ultracode Skill gives Codex a dynamic workflow layer for serious coding tasks: planning, native agents, integration, and final verification without turning the repo into a separate runner.
  8. <img src="assets/ultracode-demo.gif" alt="Ultracode running in Codex" width="100%">
  9. Use it when a task needs more than one pass: discovery, implementation, review, tests, and a final integration step. The skill tells the agent how to decide between a direct edit, a packetized workflow, or native agent delegation.
  10. Codex is the main target. Claude Code already has first-class workflow concepts; Codex has native multi-agent tools, but users still need a clean operating pattern around them. Ultracode fills that gap with one small `SKILL.md` folder.
  11. ## What it does
  12. Ultracode asks the agent to:
  13. 1. Define the goal and success criteria.
  14. 2. Decide whether the task needs direct, workflow, or delegated mode.
  15. 3. Create workflow artifacts for non-trivial work.
  16. 4. Use native agents when they are useful and allowed by the host.
  17. 5. Keep integration in the parent session.
  18. 6. Use lightweight eval contracts for risky shared surfaces.
  19. 7. Verify the result before answering, with a final audit for high-risk runs.
  20. For Codex, that means the skill can use native `spawn_agent` for independent packets, then integrate the results in the parent session.
  21. ## Install
  22. The installable skill folder is `ultracode/`.
  23. ### Codex
  24. ```bash
  25. mkdir -p "${CODEX_HOME:-$HOME/.codex}/skills"
  26. cp -R ultracode "${CODEX_HOME:-$HOME/.codex}/skills/"
  27. ```
  28. Restart Codex after installing.
  29. ### Claude Code
  30. ```bash
  31. mkdir -p "$HOME/.claude/skills"
  32. cp -R ultracode "$HOME/.claude/skills/"
  33. ```
  34. ### Antigravity
  35. Workspace install:
  36. ```bash
  37. mkdir -p .agents/skills
  38. cp -R /path/to/ultracode .agents/skills/
  39. ```
  40. User install:
  41. ```bash
  42. mkdir -p "$HOME/.gemini/antigravity/skills"
  43. cp -R ultracode "$HOME/.gemini/antigravity/skills/"
  44. ```
  45. ## Usage
  46. Start with the short form:
  47. ```text
  48. Use $ultracode to build this feature end to end.
  49. ```
  50. You do not have to manually design the workflow or ask for subagents. Ultracode decides whether the task needs a direct edit, a workflow, or native agents.
  51. For non-trivial Codex tasks, `$ultracode` is delegated-workflow intent: when useful native agents are available, Ultracode should prefer a small bounded fan-out instead of doing every independent packet in one session.
  52. If you want to force a delegated run, you can still say it directly:
  53. ```text
  54. Use $ultracode. Split this across agents where it is safe, keep integration in the parent session, and verify the final patch.
  55. ```
  56. ## Modes
  57. | Mode | Use it for | Behavior |
  58. | --- | --- | --- |
  59. | Direct | Small, clear edits | No workflow files unless needed. Run the narrowest useful check. |
  60. | Workflow | Multi-step work without useful delegation | Write plan, packet, result, integration, and final report files. |
  61. | Delegated | Independent packets where native agents are available | Spawn bounded agents, keep the critical path local, integrate results, verify. |
  62. ## Workflow files
  63. For non-trivial tasks, Ultracode writes plain Markdown and JSON:
  64. ```text
  65. .workflow/ultracode/<run-slug>/
  66. plan.md
  67. orchestration.md
  68. state.json
  69. packets/
  70. results/
  71. integration.md
  72. final-report.md
  73. ```
  74. High-risk or cross-surface runs may also include `eval-contract.md`, `contracts/`, `handoffs/`, or `final-audit.md`.
  75. These files make the run inspectable. You can see what was delegated, what changed, what passed, and what risk remains.
  76. ## Codex behavior
  77. When Codex exposes native agent tools, Ultracode prefers real delegation over fake packet simulation.
  78. The parent session should:
  79. - keep the critical path local
  80. - spawn `explorer` agents for read-only discovery
  81. - spawn `worker` agents only with clear file ownership
  82. - prefer 2-4 sidecar agents for useful independent packets
  83. - stay under 5 total sidecar agents unless the user approves more
  84. - avoid combining `agent_type` with a full-history fork
  85. - wait only when a result blocks the next parent step
  86. - close agents after collecting their results
  87. If native agents are unavailable, blocked by policy, or not useful for the task, Ultracode falls back to workflow mode and records the concrete reason.
  88. ## Live test
  89. This skill was tested in Codex with a fresh demo repository.
  90. Result:
  91. - `$ultracode` loaded the skill
  92. - `.workflow/ultracode/...` artifacts were created
  93. - Codex used native `spawn_agent`
  94. - tests passed
  95. - the parent session integrated the agent results
  96. ## What it is not
  97. Ultracode Skill does not ship a background service, hidden runner, or required scripts. It is a small skill folder that teaches the agent how to run high-effort coding workflows with the tools already available in the current host.
  98. ## Repository name
  99. The repo is `ultracode-skill`.
  100. The skill name is `ultracode`, so users can invoke it with:
  101. ```text
  102. $ultracode
  103. ```
  104. ## Star history
  105. [![Star History Chart](https://api.star-history.com/svg?repos=PabloNAX/ultracode-skill&type=Date)](https://star-history.com/#PabloNAX/ultracode-skill&Date)
  106. ## License
  107. MIT.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.