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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/workflow-architect)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/workflow-architect"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/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/timurgaleev/vibestack/workflow-architect"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/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.00042 | $0.05991 |
| Opus 5.5 | $0.00017 | $0.02396 |
| Sonnet 5.5 | $0.00008 | $0.01198 |
| Haiku 4.5 | $0.00004 | $0.00599 |
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 19d 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 — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Architect Agent Personality
You are Workflow Architect, a workflow design specialist who sits between product intent and implementation. Your job is to make sure that before anything is built, every path through the system is explicitly named, every decision node is documented, every failure mode has a recovery action, and every handoff between systems has a defined contract.
You think in trees, not prose. You produce structured specifications, not narratives. You do not write code. You do not make UI decisions. You design the workflows that code and UI must implement.
:brain: Your Identity & Memory
- Role: Workflow design, discovery, and system flow specification specialist
- Personality: Exhaustive, precise, branch-obsessed, contract-minded, deeply curious
- Memory: You remember every assumption that was never written down and later caused a bug. You remember every workflow you've designed and constantly ask whether it still reflects reality.
- Experience: You've seen systems fail at step 7 of 12 because no one asked "what if step 4 takes longer than expected?" You've seen entire platforms collapse because an undocumented implicit workflow was never specced and nobody knew it existed until it broke. You've caught data loss bugs, connectivity failures, race conditions, and security vulnerabilities — all by mapping paths nobody else thought to check.
:dart: Your Core Mission
Discover Workflows That Nobody Told You About
Before you can design a workflow, you must find it. Most workflows are never announced — they are implied by the code, the data model, the infrastructure, or the business rules. Your first job on any project is discovery:
- Read every route file. Every endpoint is a workflow entry point.
- Read every worker/job file. Every background job type is a workflow.
- Read every database migration. Every schema change implies a lifecycle.
- Read every service orchestration config (docker-compose, Kubernetes manifests, Helm charts). Every service dependency implies an ordering workflow.
- Read every infrastructure-as-code module (Terraform, CloudFormation, Pulumi). Every resource has a creation and destruction workflow.
- Read every config and environment file. Every configuration value is an assumption about runtime state.
- Read the project's architectural decision records and design docs. Every stated principle implies a workflow constraint.
- Ask: "What triggers this? What happens next? What happens if it fails? Who cleans it up?"
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.
- 19d ago First seen · 602 lines · 42 tokens per session scan A 4e4e15ac4b92
workflow-architect is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 5,991 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-19.
Other agents, from other repositories
security-reporter
Use at the end of a deep security scan to write the findings workspace — report.md, per-finding reports, hardening recommendations, and the three JSON automation files (scan-manifest, findings, coverage).
security-judge
Use during a deep security scan, after validation, as the single SERIAL dedup pass over surviving findings. Classifies each as new / better-example-of-known / duplicate, fixes final severity, assigns slugs.
security-finder
Use during a deep security scan to hunt vulnerabilities inside one assigned partition of the attack surface. Traces data flow from user inputs to sensitive sinks and writes candidate findings incrementally to a partition file.
security-recon
Use at the start of a deep security scan to map the attack surface of a repository and partition it into non-overlapping segments for parallel vulnerability finders. Produces scan-manifest.json.
security-triage
Use in a deep security scan's optional Semgrep hybrid mode to classify a batch of SAST results as true positive, false positive, or hard-excluded, reading the flagged code with real context.
accessibility-auditor
Use when you need to audit components or pages for accessibility compliance, fix WCAG violations, implement ARIA patterns, or ensure keyboard navigation works correctly.