managing-agents

managing-agents is a skill for Claude Code from mbruhler/claude-orchestration. It costs 42 tokens per session (2,029 once invoked), scanned A, original, MIT.

An agent manager handles the lifecycle of temporary and permanent coding agents, including creating, running, promoting, and cleaning them up. Agents are separate helpers assigned to particular tasks.

In plain words
What is it for?
Use it to create custom agents, manage temporary workflow agents, promote them for future use, or understand agent namespaces and registries.
Why use it?
It removes the need to track where agents live, how they are named, and when temporary ones should be removed. It also distinguishes built-in, plugin-defined, and temporary agents.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: $skill-name invocation.

Part of the claude-orchestration plugin — 9 skills, 10 commands, 3 agents shipped together

Good fit Use it to create custom agents, manage temporary workflow agents, promote them for future use, or understand agent namespaces and registries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mbruhler/claude-orchestration/managing-agents
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.

Any agent
npx skills add mbruhler/claude-orchestration --skill managing-agents
Clone the repo
git clone --depth 1 https://github.com/mbruhler/claude-orchestration

Made for: Claude Code.

Or install claude-orchestration, the plugin that ships this one along with the rest of its 9 skills, 10 commands, 3 agents.

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 managing-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/mbruhler/claude-orchestration/managing-agents.svg)](https://agentmods.dev/skills/mbruhler/claude-orchestration/managing-agents)
Your own site
<a href="https://agentmods.dev/skills/mbruhler/claude-orchestration/managing-agents"><img src="https://agentmods.dev/badge/skills/mbruhler/claude-orchestration/managing-agents.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,029 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 117
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
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.1 $0.00042 $0.02029
Opus 5 $0.00021 $0.01014
Sonnet 5 $0.00008 $0.00406
Haiku 4.5 $0.00004 $0.00203

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

Security

Grade A, and why

managing-agents 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 8d 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.

skills/managing-agents/SKILL.md · 378 lines

How it starts

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

Managing Orchestration Agents

I manage the lifecycle of agents in the orchestration system: creation, execution, promotion, and cleanup.

When I Activate

I automatically activate when you:

  • Create or define custom agents
  • Ask about agent lifecycle
  • Mention temp agents or agent promotion
  • Want to understand agent namespacing
  • Ask "how do I create an agent?"

Agent Types

Built-in Agents

No namespace prefix, always available:

  • Explore - Codebase exploration
  • general-purpose - General-purpose tasks
  • code-reviewer - Code review
  • implementation-architect - Architecture planning
  • expert-code-implementer - Code implementation

Plugin Defined Agents

With orchestration: prefix, permanent agents in this plugin:

  • orchestration:workflow-socratic-designer
  • orchestration:workflow-syntax-designer
  • Custom agents you promote

Located in: agents/ directory Registry: agents/registry.json

Temp Agents

With orchestration: prefix, workflow-specific ephemeral agents:

  • Created during workflow design
  • Saved in temp-agents/ directory
  • Auto-cleaned after workflow execution
  • Can be promoted to permanent

Reference in workflows: $agent-name

Temp Agent Lifecycle

See temp-agents.md for complete guide.

1. Creation

Created automatically during workflow design:

---
name: security-scanner
description: Scans for security vulnerabilities
created: 2025-01-08
---

You are a security expert specializing in vulnerability detection...

Saved to: temp-agents/security-scanner.md

2. Execution

Referenced in workflow with $ prefix:

$security-scanner:"Scan codebase":findings ->
general-purpose:"Analyze {findings}"

Executed with namespace: orchestration:security-scanner

3. Promotion

After workflow completion, you can save temp agents:

Workflow complete!

Temp agents created:
  - security-scanner
  - performance-profiler

Save as permanent agents? [Y/n]

Read the full file on GitHub · 378 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 378 lines · 42 tokens per session scan A d55bf0a5c17b

Subscribe to this mod's changes

managing-agents is a skill published in the GitHub repository mbruhler/claude-orchestration (219 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 2,029 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 skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

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

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens