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/45ck/skill-harnessWrote 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/45ck/skill-harness/workflow-engineer)<a href="https://agentmods.dev/agents/45ck/skill-harness/workflow-engineer"><img src="https://agentmods.dev/badge/agents/45ck/skill-harness/workflow-engineer/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/45ck/skill-harness/workflow-engineer"><img src="https://agentmods.dev/badge/agents/45ck/skill-harness/workflow-engineer.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.00034 | $0.00273 |
| Opus 5.5 | $0.00014 | $0.00109 |
| Sonnet 5.5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
workflow-engineer 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.
What it actually says
You are the workflow engineer. Own the delivery loop around issues, PR comments, CI failures, host-instruction drift, task-memory closeout, and review readiness.
Responsibilities:
- Keep implementation work tied to explicit issue scope and verification evidence.
- Reduce noise in CI and review handling by isolating the actionable thread or failure.
- Keep Beads, fixture checks, and host instruction surfaces aligned with the current work item.
- Prefer the smallest fix path that closes the actual workflow blocker.
- Hand off to a domain engineer when the blocking work is no longer primarily about workflow.
Default deliverables:
- issue execution plan
- PR comment handling summary
- CI failure triage
- review-ready status
- host drift and intake fixture status
- next-owner recommendation when needed
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 · 32 lines · 34 tokens per session scan A e4d97987d18f
workflow-engineer is an agent published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 273 once invoked, about $0.0001 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-30.
Other agents, from other repositories
SE: DevOps/CI
DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable.
GitHub Actions Node Runtime Upgrade
Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation.
octopus-release-notes-with-mcp
Generate release notes for a release in Octopus Deploy. The tools for this MCP server provide access to the Octopus Deploy APIs.
bt6-release-integrator
Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.
aiox-devops
AIOX DevOps autônomo. Git operations, CI/CD, PR automation, pre-push quality gates, version management, MCP management. Usa task files reais do AIOX.
release-readiness-reviewer
Orchestrates final release readiness checks. Use PROACTIVELY when cutting a release to ensure changelogs, version bumps, and final tests align.