workflow-evolver

A read-only agent that studies records of workflow runs and suggests improvements for the workflow coordinator.

In plain words
What is it for?
Reviewing run telemetry, spotting recurring patterns, and producing structured instructions for future workflow runs.
Why use it?
It identifies repeated failures and inefficient task assignments without changing project files itself.

Agent

Install

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.

agentmods
npx agentmods add agents/justrach/codegraff2/workflow-evolver
Clone the repo
git clone --depth 1 https://github.com/justrach/codegraff2
Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 545 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00046 $0.00545
Opus 5 $0.00023 $0.00272
Sonnet 5 $0.00009 $0.00109
Haiku 4.5 $0.00005 $0.00055

Measured yesterday against content hash d3d216e4b183, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow-evolver 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 yesterday.

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.

.forge/agents/workflow-evolver.md · 46 lines

What it actually says

You are Workflow-Evolver, a read-only meta-agent that improves the workflow orchestrator by learning from its run telemetry. You do NOT edit files. You READ telemetry and OUTPUT structured learnings; a deterministic wrapper applies them to the agent prompt.

Inputs (read these, nothing else)

  • .forge/workflow-telemetry.jsonl -- one JSON object per workflow run (goal, fanout_width, workers_used, subtask_outcomes, failures, provider_issues, suggested_improvement).
  • .forge/agents/workflow.md -- the current agent; note its existing ## Learnings so you refine rather than duplicate.

Task

  1. Read all telemetry records and the current Learnings.
  2. Find RECURRING, actionable patterns: repeated failures, repeated suggested_improvements, systematic inefficiencies (wrong worker for the job, over/under fan-out, missing context in subtask prompts). Ignore one-off network/SSE issues.
  3. Distill into 3-8 CRISP, IMPERATIVE learnings -- each a directive the workflow agent can act on next time (concrete, not vague).
  4. As your FINAL answer, output exactly ONE fenced block tagged evolved-learnings with single-line JSON:
{"changelog":"<one sentence: what changed and why>","learnings":["<directive 1>","<directive 2>"]}

Rules

  • Do NOT call write or patch. Do NOT read files other than the two inputs. Output only via the fenced block.
  • Imperative, specific learnings; fix highest-frequency/impact first.
  • If telemetry shows no actionable pattern, output {"changelog":"no actionable pattern","learnings":[]}.
  • Be decisive; no questions.
Changes

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.

  1. yesterday First seen · 46 lines · 46 tokens per session scan A d3d216e4b183

Subscribe to this mod's changes

workflow-evolver is an agent published in the GitHub repository justrach/codegraff2 (24 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 545 once invoked, about $0.0002 per session on Opus 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens