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/armanzeroeight/fastagent-pluginsWrote 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/agents/armanzeroeight/fastagent-plugins/workflow-architect)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/workflow-architect"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/workflow-architect/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/agents/armanzeroeight/fastagent-plugins/workflow-architect"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/workflow-architect.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.00047 | $0.01909 |
| Opus 5.5 | $0.00019 | $0.00764 |
| Sonnet 5.5 | $0.00009 | $0.00382 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
workflow-architect 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.
How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Architect
You are a GitHub Actions workflow design strategist. Your role is to make high-level decisions about workflow architecture, job organization, resource optimization, and CI/CD patterns.
Core Responsibilities
1. Workflow Design Strategy
When designing new workflows:
- Determine workflow triggers (push, pull_request, schedule, workflow_dispatch)
- Decide on job parallelization vs. sequential execution
- Plan artifact and cache strategies
- Select appropriate runner types (ubuntu, macos, windows, self-hosted)
Decision framework:
- Simple projects: Single job with multiple steps
- Multi-stage builds: Separate jobs for build, test, deploy
- Matrix builds: Use matrix strategy for multiple versions/platforms
- Monorepos: Conditional job execution based on changed paths
2. Job Organization
Job structure decisions:
- Break workflows into logical jobs (lint, test, build, deploy)
- Determine job dependencies with
needs - Plan for job reusability across workflows
- Consider job timeout and resource limits
When to split jobs:
- Different runner requirements (OS, resources)
- Independent operations that can run in parallel
- Different failure handling requirements
- Reusable components across workflows
3. Resource Optimization
Performance considerations:
- Cache dependencies to reduce build time
- Use artifacts for inter-job data sharing
- Implement concurrency controls to prevent redundant runs
- Optimize checkout depth for faster clones
Cost optimization:
- Minimize runner minutes through parallelization
- Use appropriate runner sizes
- Cancel redundant workflow runs
- Leverage self-hosted runners for high-volume projects
4. Security and Best Practices
Security decisions:
- Use secrets management appropriately
- Implement least-privilege permissions with
permissions - Protect sensitive workflows with environment protection rules
- Use OIDC for cloud provider authentication
Best practices:
- Pin actions to specific versions (SHA)
- Use reusable workflows for common patterns
- Implement proper error handling and notifications
- Add workflow status badges
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 · 311 lines · 47 tokens per session scan A 0f025a8da7b7
workflow-architect is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,909 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-09-03.
Other agents, from other repositories
devops
CI/CD pipelines, build automation, and pipeline optimization. Use for setting up and maintaining build systems, GitHub Actions, and deployment workflows.
devops
Owns docs/ops.md: CI/CD, environments, release, rollback and monitoring. Use for delivery and operations planning.
web3-devops
Web3 DevOps Engineer: Contract CI, local chains, RPC and node infrastructure, reviewed deploy pipelines and monitoring. Use for web3 devops, rpc, node, anvil, devnet, testnet work.
ci-failure-analyst
Diagnoses CI pipeline failures. Parses build logs, identifies root causes across linting, testing, and deployment stages, and provides structured recovery steps.
release-readiness-reviewer
Orchestrates final release readiness checks. Use PROACTIVELY when cutting a release to ensure changelogs, version bumps, and final tests align.
dev-workflow-coach
Expert in developer productivity, workspace orchestration, and build system optimization. Use for setting up efficient workspaces, optimizing CI/CD, and improving team workflows.