agent-orchestration-improve-agent

agent-orchestration-improve-agent is a skill for Claude Code from marysatasselshaped667/skills-collection-1. It costs 25 tokens per session (2,110 once invoked), scanned A, a copy of agent-orchestration-improve-agent, MIT.

A structured process for improving an existing AI agent through performance analysis, prompt changes, testing, and iteration.

In plain words
What is it for?
Use it to establish baseline metrics, analyze failure patterns, run comparisons or evaluation suites, and release improvements in controlled stages.
Why use it?
It helps identify why an agent fails and measure whether changes make it more reliable.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to establish baseline metrics, analyze failure patterns, run comparisons or evaluation suites, and release improvements in controlled stages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/marysatasselshaped667/skills-collection-1/agent-orchestration-improve-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.

Any agent
npx skills add marysatasselshaped667/skills-collection-1 --skill agent-orchestration-improve-agent
Clone the repo
git clone --depth 1 https://github.com/marysatasselshaped667/skills-collection-1

Made for: Claude Code.

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 agent-orchestration-improve-agent

README.md
[![agentmods](https://agentmods.dev/badge/skills/marysatasselshaped667/skills-collection-1/agent-orchestration-improve-agent/github.svg)](https://agentmods.dev/skills/marysatasselshaped667/skills-collection-1/agent-orchestration-improve-agent)
Your own site
<a href="https://agentmods.dev/skills/marysatasselshaped667/skills-collection-1/agent-orchestration-improve-agent"><img src="https://agentmods.dev/badge/skills/marysatasselshaped667/skills-collection-1/agent-orchestration-improve-agent/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.

agentmods 80×15 button for agent-orchestration-improve-agent

Your own site · 80×15
<a href="https://agentmods.dev/skills/marysatasselshaped667/skills-collection-1/agent-orchestration-improve-agent"><img src="https://agentmods.dev/badge/skills/marysatasselshaped667/skills-collection-1/agent-orchestration-improve-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,110 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.
Origin 91% copy Near-identical to another mod 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.00025 $0.02110
Opus 5 $0.00013 $0.01055
Sonnet 5 $0.00005 $0.00422
Haiku 4.5 $0.00003 $0.00211

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

Security

Grade A, and why

agent-orchestration-improve-agent 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 12d 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.

Origin

This is a copy

91% identical to agent-orchestration-improve-agent — 7 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.

SKILLS/agent-orchestration-improve-agent/SKILL.md · 353 lines

How it starts

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

Agent Performance Optimization Workflow

Systematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.

[Extended thinking: Agent optimization requires a data-driven approach combining performance metrics, user feedback analysis, and advanced prompt engineering techniques. Success depends on systematic evaluation, targeted improvements, and rigorous testing with rollback capabilities for production safety.]

Use this skill when

  • Improving an existing agent's performance or reliability
  • Analyzing failure modes, prompt quality, or tool usage
  • Running structured A/B tests or evaluation suites
  • Designing iterative optimization workflows for agents

Do not use this skill when

  • You are building a brand-new agent from scratch
  • There are no metrics, feedback, or test cases available
  • The task is unrelated to agent performance or prompt quality

Instructions

  1. Establish baseline metrics and collect representative examples.
  2. Identify failure modes and prioritize high-impact fixes.
  3. Apply prompt and workflow improvements with measurable goals.
  4. Validate with tests and roll out changes in controlled stages.

Safety

  • Avoid deploying prompt changes without regression testing.
  • Roll back quickly if quality or safety metrics regress.

Phase 1: Performance Analysis and Baseline Metrics

Comprehensive analysis of agent performance using context-manager for historical data collection.

1.1 Gather Performance Data

Use: context-manager
Command: analyze-agent-performance $ARGUMENTS --days 30

Collect metrics including:

  • Task completion rate (successful vs failed tasks)
  • Response accuracy and factual correctness
  • Tool usage efficiency (correct tools, call frequency)
  • Average response time and token consumption
  • User satisfaction indicators (corrections, retries)
  • Hallucination incidents and error patterns

1.2 User Feedback Pattern Analysis

Identify recurring patterns in user interactions:

Read the full file on GitHub · 353 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. 12d ago First seen · 353 lines · 25 tokens per session scan A 9dbfc6717782

Subscribe to this mod's changes

agent-orchestration-improve-agent is a skill published in the GitHub repository marysatasselshaped667/skills-collection-1 (1 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 2,110 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to agent-orchestration-improve-agent, differing in 7 lines, and is treated as a copy.