Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Suraj1235/open-dynamic-workflows --skill ultracodegit clone --depth 1 https://github.com/Suraj1235/open-dynamic-workflowsWrote 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/skills/suraj1235/open-dynamic-workflows/ultracode)<a href="https://agentmods.dev/skills/suraj1235/open-dynamic-workflows/ultracode"><img src="https://agentmods.dev/badge/skills/suraj1235/open-dynamic-workflows/ultracode/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/suraj1235/open-dynamic-workflows/ultracode"><img src="https://agentmods.dev/badge/skills/suraj1235/open-dynamic-workflows/ultracode.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.00458 |
| Opus 5.5 | $0.00022 | $0.00183 |
| Sonnet 5.5 | $0.00011 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
ultracode 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 1mo 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.
What it actually says
Ultracode Through Open Dynamic Workflows for Antigravity
This is the Antigravity-facing ultracode alias for Open Dynamic Workflows. It routes the expected ultracode entrypoint through the same ODW daemon, MCP tools, plugin rules, and native fallback as the odw skill.
Step 0: Check the daemon
Run:
node scripts/daemon-bridge.js --check
- Exit 0: use the daemon path.
- Exit 1 with auth guidance: tell the user to copy
~/.odw/daemon.tokenintoODW_DAEMON_TOKENor the host setting. - Exit 1 because the daemon is offline: tell the user to run
odw-daemon startorodw-daemon doctor antigravity.
Daemon Path
- Prefer MCP tools when available: call
odw_health, thenodw_runfor direct execution orodw_planfirst when the user wants to review the plan, the task is expensive, or mutation risk is high. - If MCP tools are unavailable but the daemon is reachable, use the local bridge:
node scripts/daemon-bridge.js plan "<task>"node scripts/daemon-bridge.js exec plan.jsonnode scripts/daemon-bridge.js status <workflowId>node scripts/daemon-bridge.js result <workflowId>
- Report the workflow id, topology, agent count, cost/time estimate, and final synthesized result. Do not redo the same work manually while ODW is running it.
Antigravity-Native Fallback
If the daemon is unavailable, state that full ultracode requires the daemon, then use Antigravity's native planning and editing flow: discovery -> parallel work -> adversarial verification -> synthesis.
Never include secrets in prompts, plans, logs, or workflow artifacts.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 37 lines · 56 tokens per session scan A ffe1f513e6b7
ultracode is a skill published in the GitHub repository Suraj1235/open-dynamic-workflows (50 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 458 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
local-llm-tool
A local LLM execution tool. Requests text generation and chat from models on GPU via Ollama or vLLM. Use when: Use when: on-premise inference, calling Ollama endpoints, or needing summaries and generation with local models.
understand-codebase
Understand an unfamiliar codebase or plan a change safely, using Spine's deterministic knowledge-graph MCP tools. Reach for this before answering structural questions about a repo you don't know, before editing code, or when debugging — it hands you engineering decisions (what a change breaks, what's untested, where a…
social
Process blog posts into platform-optimized social media share material, and analyze external X posts for reply vs QT strategy, reply drafts, and follow recommendations among repliers. Use when the user wants tweets, LinkedIn, Bluesky, share schedules, or when they paste an x.com/twitter status URL and want reply…
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
continue
Autonomous work — find and execute ready tasks.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.