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/moabualruz/agent-workflow-kit/workflownpx skills add moabualruz/agent-workflow-kit --skill workflowgit clone --depth 1 https://github.com/moabualruz/agent-workflow-kitWhat 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.00018 | $0.00403 |
| Opus 5 | $0.00009 | $0.00201 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
workflow 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 2d 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
Workflow
Create, persist, and run a generated workflow through the shared CLI:
agent-workflow-kit workflow "<task>" --json
Use --project-root "${AGENT_WORKFLOW_KIT_PROJECT_ROOT:-$PWD}" when the active Antigravity workspace root is ambiguous.
Ultracode & multi-phase orchestration
Authoring and running a workflow spins up many subagents and spends real tokens. Author a workflow only when the user typed "workflow"/"workflows", asked for multi-agent orchestration, when the ultracode standing opt-in or keyword trigger applies, when a skill or command instructed it, or when the user named a saved workflow. Otherwise act directly or offer a workflow and let the user opt in.
Ultracode has three separate meanings in this kit. The standing opt-in is the persisted project behavior (agent-workflow-kit ultracode on|off|status, stored in .agent-workflow-kit/config.json) that author-runs a workflow for substantive tasks by default. The keyword trigger is recorded separately as ultracodeKeywordTriggerEnabled and is disabled when workflows are disabled. Model effort is host-owned: this standalone CLI reports model effort as unsupported and records ultracodeEffortMode: "orchestration-only" when orchestration is enabled. Turn ultracode on only when the user asks; when off, revert to the opt-in gate.
For larger work, decompose into a sequence of workflows (understand -> design -> implement -> review), inspecting each run with workflow-run --stream, workflow-events --follow, or workflow-status --tree between phases rather than one giant run.
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.
- 2d ago First seen · 24 lines · 18 tokens per session scan A 369b7e101a95
workflow is a skill published in the GitHub repository moabualruz/agent-workflow-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
team-communication-protocols
Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing communication norms for a newly spawned team, when deciding whether to send a direct message or a broadcast, when a team-lead…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
team-composition-patterns
Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagenttype for each role to…
implementer
Delegate a coding task to Google's Antigravity CLI (agy staffer, fast Gemini), which edits the working tree directly and can perform explicitly requested Git delivery. Use when the user says /agy:implementer, "have agy fix/build X", or wants to hand a well-scoped coding task to the agy staffer instead of doing it in…