workerflow-internal-workflow

workerflow-internal-workflow is a skill for Claude Code, Codex from agentscope-ai/AgentTeams. It costs 52 tokens per session (2,250 once invoked), scanned A, original, Apache-2.0.

A decision guide for a worker choosing between doing work directly, using short-lived internal helpers, or creating a temporary custom worker.

In plain words
What is it for?
Use it to choose an internal workflow based on whether the work needs parallel inspection, custom instructions, a workspace, or a skill set.
Why use it?
It prevents unnecessary agent creation and separates private parallel work from tasks that need a persistent team member or leader approval.

Skill for Claude CodeCodex

About the project

AgentTeams is a runtime platform where multiple AI agents collaborate in shared Matrix rooms under the coordination of a manager. It is for human-supervised or enterprise workflows that need visible, auditable cooperation among agents running on different runtimes, with shared files and centralized traffic management.

agentscope-ai/AgentTeams · 5,564 stars · on GitHub

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 skills/agentscope-ai/agentteams/worker-internal-workflow
Any agent
npx skills add agentscope-ai/AgentTeams --skill worker-internal-workflow
Clone the repo
git clone --depth 1 https://github.com/agentscope-ai/AgentTeams

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for workerflow-internal-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/agentscope-ai/agentteams/worker-internal-workflow.svg)](https://agentmods.dev/skills/agentscope-ai/agentteams/worker-internal-workflow)
Your own site
<a href="https://agentmods.dev/skills/agentscope-ai/agentteams/worker-internal-workflow"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentteams/worker-internal-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,250 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.00052 $0.02250
Opus 5 $0.00026 $0.01125
Sonnet 5 $0.00010 $0.00450
Haiku 4.5 $0.00005 $0.00225

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

Security

Grade A, and why

workerflow-internal-workflow 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 5d 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.

plugins/workerflow/skills/agent/worker-internal-workflow/SKILL.md · 241 lines

How it starts

The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Worker Internal Workflow

Use this skill before splitting work inside a single Worker. WorkerFlow is not TeamHarness delegation.

Decision

Need Path
Current Worker can do it directly No subagent
Same Worker needs short parallel inspection QwenPaw native subagent
Same Worker needs visible fan-out to custom roles, workspaces, AGENTS.md, or skills Dynamic workflow via worker_agentflow workflow_run
Same Worker needs one manually controlled temporary subagent create_temp_agent directly
Work needs a persistent team member or Leader acceptance Do not use WorkerFlow; use the team workflow

Native Subagent

Use QwenPaw native subagents for short internal parallelism. The current Worker still owns the final result.

Do not create a temporary agent when no custom prompt, workspace, or skill set is required.

Temporary QwenPaw Agent

Use worker_agentflow with workflow_run when a custom AgentSpec-style template has already been placed in the default QwenPaw workspace:

<QWENPAW_WORKING_DIR>/workspaces/default/subagents/<role>/
  AGENTS.md
  PROFILE.md        # optional
  SOUL.md           # optional
  skills/
    <skill-id>/
      SKILL.md

Use list_subagents first when you need to discover the templates available in the default workspace. Use create_temp_agent directly only when you need manual control outside a dynamic workflow.

Subagent template rules:

  • AGENTS.md should tell the temporary agent to begin analysis immediately.
  • AGENTS.md should forbid greetings, self-introductions, and capability summaries.
  • AGENTS.md should define the subagent's focus area so the Worker can send the complete source input instead of manually slicing the input.
  • When multiple subagent results will be merged, each AGENTS.md should require the same fixed output shape.

Dynamic workflow lifecycle:

  1. Call workflow_run with the explicit current DM/conversation roomId, title, source input, optional merge.instruction, and either subagents or DAG nodes.
  2. Each subagent or node must name a default-workspace template with subagent and a bounded task.
  3. workflow_run starts the Matrix card, creates tmp-... subagents, creates the run-level shared directory, stores workflow.json, and returns submitInstructions for nodes that are ready now.
  4. Send each returned submitPrompt to its agentId using the available QwenPaw agent communication tools.
  5. When a subagent finishes, call workflow_update with a steps row whose id matches the node id, status is done, and summary contains the short result.
  6. For DAG nodes, inspect every workflow_update response. If it returns readyInstructions, immediately send each returned submitPrompt to its agentId.
  7. Use workflow_update at meaningful phase changes: submitted, running, retrying, merging, cleanup, done, or failed.
  8. Retry a timed-out subagent once when the task is still useful.
  9. Mark subagents that still fail as missing or failed in the merged result.
  10. Merge subagent results into the current Worker's own output.
  11. Delete every temporary agent with delete_temp_agent.
  12. Call workflow_finish or workflow_fail.
  13. After merging, either keep the shared run directory as evidence or remove it with cleanup_shared.

Read the full file on GitHub · 241 lines

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. 5d ago First seen · 241 lines · 52 tokens per session scan A aec6fbe706d4

Subscribe to this mod's changes

workerflow-internal-workflow is a skill published in the GitHub repository agentscope-ai/AgentTeams (5,564 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 2,250 once invoked, about $0.0003 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 skills, from other repositories

plan-ceo-review

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…

GCWing/BitFun · 143 tokens

ship

Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…

GCWing/BitFun · 88 tokens

design-review

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…

GCWing/BitFun · 125 tokens

plan-eng-review

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…

GCWing/BitFun · 116 tokens

autoplan

Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…

GCWing/BitFun · 152 tokens

retro

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively…

GCWing/BitFun · 76 tokens