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.
git clone --depth 1 https://github.com/moabualruz/agent-workflow-kitWrote 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/commands/moabualruz/agent-workflow-kit/workflow-run)<a href="https://agentmods.dev/commands/moabualruz/agent-workflow-kit/workflow-run"><img src="https://agentmods.dev/badge/commands/moabualruz/agent-workflow-kit/workflow-run/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/commands/moabualruz/agent-workflow-kit/workflow-run"><img src="https://agentmods.dev/badge/commands/moabualruz/agent-workflow-kit/workflow-run.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.00000 | $0.00488 |
| Opus 5.5 | $0.00000 | $0.00195 |
| Sonnet 5.5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
workflow-run 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 2mo 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
Run the requested Agent Workflow Kit workflow.
Use plugin tools when available. CLI fallback:
agent-workflow-kit workflow-run no-write-probe --json
agent-workflow-kit workflow-run <workflow> --args-json '{"key":"value"}' --json
agent-workflow-kit workflow-run <workflow> --stream --json
agent-workflow-kit workflow-status <run-id> --json
agent-workflow-kit workflow-events <run-id> --json
agent-workflow-kit workflow-events <run-id> --follow
agent-workflow-kit workflow-resume <run-id> --json
agent-workflow-kit workflow-stop <run-id> --json
agent-workflow-kit workflows --json
agent-workflow-kit deep-research "<question>" --json
agent-workflow-kit ultracode status --json
Saved workflow scripts read structured args from context.args.
Use workflow-run --stream --json for long launches: event lines go to stderr and the final run JSON stays on stdout.
Use workflow-events --follow for an existing run id instead of repeatedly polling.
Executable smoke:
generated_json="$(agent-workflow-kit workflow "file command generated" --json)"
generated_name="$(printf '%s' "$generated_json" | bun -e 'const fs = require("fs"); const data = JSON.parse(fs.readFileSync(0, "utf8")); console.log(data.args.workflow.name);')"
printf '%s\n' "$generated_json"
agent-workflow-kit workflow-run "$generated_name" --json
run_json="$(agent-workflow-kit workflow-run no-write-probe --json)"
run_id="$(printf '%s' "$run_json" | bun -e 'const fs = require("fs"); const data = JSON.parse(fs.readFileSync(0, "utf8")); console.log(data.runId);')"
printf '%s\n' "$run_json"
agent-workflow-kit workflow-status "$run_id" --json
agent-workflow-kit workflow-events "$run_id" --json
agent-workflow-kit workflow-resume "$run_id" --json
agent-workflow-kit workflow-stop "$run_id" --json
agent-workflow-kit workflows --json
agent-workflow-kit deep-research "file-command-smoke" --json
agent-workflow-kit ultracode status --json
Return only run id, status, and artifact path.
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.
- 2mo ago First seen · 43 lines · 0 tokens per session scan A 192d342f2863
workflow-run is a command published in the GitHub repository moabualruz/agent-workflow-kit (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 488 tokens. 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.
workflow-run compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| workflow-runmoabualruz/agent-workflow-kit | Command | 2 | 1mo ago | MIT | A | 0 | Claude Code |
| code-reviewraja21068/AutoResearch | Command | 2 | 5mo ago | MIT | A | 10 | Claude Code |
| evalraja21068/AutoResearch | Command | 2 | 5mo ago | MIT | A | 5 | Claude Code |
| instinct-importraja21068/AutoResearch | Command | 2 | 5mo ago | MIT | A | 5 | Claude Code |
| rust-testraja21068/AutoResearch | Command | 2 | 5mo ago | MIT | A | 9 | Claude Code |
| skill-createraja21068/AutoResearch | Command | 2 | 5mo ago | MIT | A | 6 | Claude Code |
| test-coverageraja21068/AutoResearch | Command | 2 | 5mo ago | MIT | A | 5 | Claude Code |