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 skills add proffesor-for-testing/agentic-qe --skill workflow-automationgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/workflow-automation)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/workflow-automation"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/workflow-automation/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/proffesor-for-testing/agentic-qe/workflow-automation"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/workflow-automation.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.00053 | $0.00408 |
| Opus 5.5 | $0.00021 | $0.00163 |
| Sonnet 5.5 | $0.00011 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
workflow-automation 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 1mo 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.
This is a copy
100% identical to workflow-automation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Workflow Automation Skill
Purpose
Create and execute automated workflows for complex multi-step processes.
When to Trigger
- Multi-step automated processes
- Reusable workflow creation
- Complex task orchestration
- CI/CD pipeline setup
Commands
Create Workflow
npx claude-flow workflow create --name "deploy-flow" --template ci
Execute Workflow
npx claude-flow workflow execute --name "deploy-flow" --env production
List Workflows
npx claude-flow workflow list
Export Template
npx claude-flow workflow export --name "deploy-flow" --format yaml
View Status
npx claude-flow workflow status --name "deploy-flow"
Built-in Templates
| Template | Description |
|---|---|
ci |
Continuous integration pipeline |
deploy |
Deployment workflow |
test |
Testing workflow |
release |
Release automation |
review |
Code review workflow |
Workflow Structure
name: example-workflow
steps:
- name: analyze
agent: researcher
task: "Analyze requirements"
- name: implement
agent: coder
depends: [analyze]
task: "Implement solution"
- name: test
agent: tester
depends: [implement]
task: "Write and run tests"
Best Practices
- Define clear step dependencies
- Use appropriate agent types per step
- Include validation gates
- Export workflows for reuse
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.
- 1mo ago First seen · 79 lines · 53 tokens per session scan A 8ead452fce5b
workflow-automation is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (508 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 408 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to workflow-automation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…