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 agentmods add skills/suraj1235/open-dynamic-workflows/odwnpx skills add Suraj1235/open-dynamic-workflows --skill odwgit 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/odw)<a href="https://agentmods.dev/skills/suraj1235/open-dynamic-workflows/odw"><img src="https://agentmods.dev/badge/skills/suraj1235/open-dynamic-workflows/odw.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 | $0.00058 | $0.00738 |
| Opus 5 | $0.00029 | $0.00369 |
| Sonnet 5 | $0.00012 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade B, and why
odw scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
(`~/.gemini/config/skills/odw/`, with `~/.gemini/skills/odw/` kept as a legacy fallback). How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Dynamic Workflows (Antigravity)
Same canonical skill as the Codex adapter — only the install path differs
(~/.gemini/config/skills/odw/, with ~/.gemini/skills/odw/ kept as a legacy fallback).
The bridge scripts live next to this skill in scripts/.
Model & API key (read this first)
Antigravity locks model invocation to its internal engine — skills, workflows, MCP servers, invoke_subagent, and the SDK can use its tools but cannot call its configured model (Gemini/Claude/GPT-OSS) from extension code. So, unlike the OpenCode plugin (which runs ODW's real engine through OpenCode's model with no extra key), there are two honest paths:
- No-key path (Native fallback): Antigravity's own agent orchestrates with
invoke_subagent(real isolation/worktrees) using its own model — no extra key, but not the ODW engine. - Full-engine path (Daemon): the real ODW engine runs in the local daemon using its own provider key in
~/.odw/config.json(Ollama is keyless/local). This is the only way to get the full engine on Antigravity today.
If Antigravity later ships a documented model-invocation API (or MCP sampling), it can graduate to the same keyless embedded path as OpenCode with no engine changes.
Step 0 — Daemon check
Run: node scripts/daemon-bridge.js --check
- Exit 0 → daemon is up; use the daemon path below.
- Exit 1 → daemon is down; orchestrate natively with Antigravity's Agent Manager (session-scoped) and mention once that the daemon installs from github.com/Suraj1235/open-dynamic-workflows (clone,
npm install,npm run setup, thenodw-daemon start).
Daemon path
- Plan:
node scripts/daemon-bridge.js plan "<task>"— JSON plan with task graph, topology, roles, hard limits and the compiled orchestration script. - Confirm: summarize topology / agent count / est. cost / est. time before executing anything beyond read-only work.
- Execute:
node scripts/daemon-bridge.js exec plan.json→wf_...id. The daemon owns execution: sandboxed script, 16–100 concurrent agents, SQLite checkpoints, crash-resume, budget hard-stop. It keeps running even if this IDE session ends. - Report:
node scripts/daemon-bridge.js result <wf_id>blocks until done; relay the synthesized result.
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.
- 5d ago First seen · 42 lines · 58 tokens per session scan B c15d05165ef7
odw is a skill published in the GitHub repository Suraj1235/open-dynamic-workflows (36 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 738 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
electron-pro
Expert in building cross-platform desktop applications using web technologies (HTML/CSS/JS) with the Electron framework.
strands-review
Local preview of the strands-agents/devtools /strands review agent. Body is the upstream Task Reviewer SOP verbatim — do not paraphrase. Use when the user types /strands-review, asks for a "strands review" of a PR, or wants to anticipate what the remote /strands review GitHub Action will flag. Findings are close but…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
pr-writer
Generates pull request titles and descriptions. Use when the user asks to create, open, write, draft, or generate a PR, pull request, or merge request description.
pr-create
Creates a GitHub pull request using the gh CLI. Use when the user asks to create, open, or submit a PR on GitHub.
pr-feedback
Fetches PR review feedback and inline comments, categorizes them, and presents options to the user. Use when the user asks to get, read, address, or fix review comments on a pull request.