Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ArchAstro/archagentsnpx agentmods add skills/archastro/archagents/build-workflowWrote 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/archastro/archagents/build-workflow)<a href="https://agentmods.dev/skills/archastro/archagents/build-workflow"><img src="https://agentmods.dev/badge/skills/archastro/archagents/build-workflow/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/archastro/archagents/build-workflow"><img src="https://agentmods.dev/badge/skills/archastro/archagents/build-workflow.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.00085 | $0.02557 |
| Opus 5.5 | $0.00034 | $0.01023 |
| Sonnet 5.5 | $0.00017 | $0.00511 |
| Haiku 4.5 | $0.00009 | $0.00256 |
Grade A, and why
build-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- archagent-build-workflow — 91% identical, 33 lines differ
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ArchAstro Workflow Builder
Create, edit, and deploy workflows — multi-step processes that agents execute via routines.
This skill assumes the ArchAgent CLI is already installed and authenticated. Use the /archagents:install and /archagents:auth commands in this same plugin instead of trying to install or authenticate the CLI manually inside this skill.
What is a Workflow?
A workflow is a directed graph of nodes that defines a multi-step process. Use the dedicated top-level workflow resource for authoring: archagent list workflows, describe workflow, create workflow, update workflow, validate workflow, and describe workflowdocs. Workflows are then attached to agent routines for execution.
Always Start with State
Every invocation must begin by understanding the current context:
archagent auth status
archagent list agents
Determine:
- Which agent will run this workflow?
- Is this a new workflow or an update to an existing one?
- What trigger should start it? (schedule, webhook, manual, message event)
Routing
Workflow commands not exposed in the current archagent build
The source tree has dedicated top-level workflow commands, but some archagent builds may not expose them yet. Verify first:
archagent list workflows
archagent describe workflowdocs
If those commands are unavailable, do not keep insisting on them. Fall back to the config-managed workflow path and explain that the dedicated workflow resource exists in source but is not wired into the current binary.
User wants to create a new workflow
Phase 1: Gather requirements
Understand the workflow before writing any config:
- What triggers it? (cron schedule, webhook, message, manual)
- What are the steps? (in plain language)
- Are there branches or conditions?
- Does it need to call external APIs?
- Does it need to send emails, Slack messages, or other notifications?
- Does it loop over a collection?
Discover available events to understand what can trigger the workflow and what data the trigger provides:
archagent list events
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 · 304 lines · 85 tokens per session scan A 68ad1ad67f8e
build-workflow is a skill published in the GitHub repository ArchAstro/archagents (7 stars, last pushed 29d ago), licensed MIT. It adds 85 tokens to every session and 2,557 once invoked, about $0.0003 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-31.
Other skills, from other repositories
test-review
You are an expert DataHub test reviewer. Your role is to evaluate pytest smoke tests against established testing standards, identify issues, and provide actionable feedback.
sre-agent
Deploy or update the SRE Agent on Omnara, a production investigator that diagnoses issues across AWS and source code and reports the likely cause with evidence. Use when the user asks to deploy, set up, update, or remove the SRE agent.
browser-agent
Build and deploy a Browser Agent on Omnara, a long-running agent that signs in to web apps with stored credentials and works in a real browser, overnight if needed. Interviews the user about the job, sign-ins, schedule, and Slack or Discord first. Use when the user asks to build, deploy, set up, update, or remove a…
email-agent
Deploy or update the Email Agent on Omnara, an agent with its own email address that people can email, Cc, or @mention, built on Primitive's hosted email functions and MCP server. Use when the user asks to deploy, set up, update, customize, or remove the email agent.
linkedin-signal-agent
Deploy or update the LinkedIn Signal Agent on Omnara, an agent that scrapes LinkedIn posts (keyword search plus tracked company and profile feeds) and delivers a daily digest. Use when the user asks to deploy, set up, update, or remove the LinkedIn signal agent.
posthog-analytics-agent
Deploy or update the PostHog Analytics Agent on Omnara, an agent that queries a PostHog project through PostHog's MCP server and delivers a daily usage report. Use when the user asks to deploy, set up, update, or remove the PostHog analytics agent.