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/TreeX-X/WorkFlowXWrote 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/plugins/treex-x/workflowx/claude)<a href="https://agentmods.dev/plugins/treex-x/workflowx/claude"><img src="https://agentmods.dev/badge/plugins/treex-x/workflowx/claude/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/plugins/treex-x/workflowx/claude"><img src="https://agentmods.dev/badge/plugins/treex-x/workflowx/claude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
workflowx 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 27d 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 workflowx — 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
{
"name": "workflowx",
"version": "1.0.0",
"description": "Multi-agent orchestration framework with Socratic requirements discovery, task notes PRD management, and structured quality evaluation",
"author": {
"name": "TreeX"
},
"homepage": "https://github.com/TreeX-X/workflowX",
"repository": "https://github.com/TreeX-X/workflowX",
"license": "MIT",
"keywords": [
"multi-agent",
"orchestration",
"workflow",
"planning",
"evaluation",
"task-notes",
"requirements-discovery"
]
}
What it installs
The manifest is a name and a version. 9 skills, 5 commands, 4 agents travel with it, and installing the plugin installs all of them — 814 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill orchestrateX A 29 tokens
- Skill auditX A 18 tokens
- Skill noteX A 25 tokens
- Skill engineeringX A 15 tokens
- Skill proseX A 13 tokens
- Skill socratesX A 19 tokens
- Skill specX A 13 tokens
- Skill diag-example-skill A 41 tokens
- Skill huashu-design A 505 tokens
- Command xdel A 5 tokens
- Command xflow A 5 tokens
- Command xarch A 5 tokens
- Command xdo A 5 tokens
- Command xstatus A 5 tokens
- Agent coderX A 31 tokens
- Agent evaluatorX A 13 tokens
- Agent coder-teammate A 33 tokens
- Agent evaluator-teammate A 34 tokens
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.
- 27d ago Changed f2c500e2d7ed
- 1mo ago First seen · 21 lines scan A 093f883ae0de
workflowx is a plugin published in the GitHub repository TreeX-X/WorkFlowX (53 stars, last pushed 7d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 100% identical to workflowx, differing in 0 lines, and is treated as a copy.
Other plugins, from other repositories
good-bad-ugly
The Good, the Bad and the Ugly — tiered multi-agent orchestration for Claude Code. The Good (brain) plans and verifies, the Bad (judgment executor) handles work needing taste, the Ugly (mechanical executor) does the grunt work — in parallel herdr panes with fenced scopes.
kiln
Multi-model software creation pipeline. A conversation becomes running, tested software — an interactive brainstorm, then an autonomous build: GPT-5.6 writes the code, Claude shapes the plans and interfaces, and each family inspects the work of the other.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
the-council
Catch blind spots in architecture decisions with multi-perspective analysis that learns from your project history.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.