Agent skill · Audited from source
Workflow Optimizer
skill · hoangsonww/Claude-Code-Agent-MonitorMIT licenceAudited 16 Oct 2026 · source 1f059c400d07
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 1f059c400d07 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Analyze workflow patterns using the Agent Monitor's workflow intelligence API — orchestration DAGs, tool flow transitions, subagent effectiveness, model delegation patterns, error propagation by depth, concurrency…
Cite
Cite this page
ModelsAtlas. “Workflow Optimizer (hoangsonww/Claude-Code-Agent-Monitor)”. Retrieved 16 Oct 2026. https://modelsatlas.com/skills/hoangsonww/workflow-optimizer
Trust audit
Audit 0.4.1 · source read 16 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 1f059c400d07 · 16 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherhoangsonww GitHub userOwner of the repository this skill is read from
- Source folderhoangsonww/Claude-Code-Agent-Monitor/plugins/ccam-productivity/skills/workflow-optimizerThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict1f059c400d07A new audit runs when the source changes
- Repository statusNot archivedLast push 4 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Analyze workflow patterns using the Agent Monitor's workflow intelligence API — orchestration DAGs, tool flow transitions, subagent effectiveness, model delegation patterns, error propagation by depth, concurrency…
---
name: workflow-optimizer
description: >
Analyze workflow patterns using the Agent Monitor's workflow intelligence
API — orchestration DAGs, tool flow transitions, subagent effectiveness,
model delegation patterns, error propagation by depth, concurrency lanes,
compaction impact, and agent co-occurrence. Produces prioritized optimization
recommendations with quantified impact.
---
# Workflow Optimizer
Analyze Claude Code workflows using the Agent Monitor's workflow intelligence engine.
## Input
The user provides: **$ARGUMENTS**
Options: "analyze", a session ID for single-session analysis, or a focus: "tools", "subagents", "cost", "errors".
## Data Sources
| Endpoint | Returns |
|----------|---------|
| `GET /api/sessions?limit=100` | Session list with metadata |
| `GET /api/workflows/{sessionId}` | **11 workflow datasets** (see below) |
| `GET /api/analytics` | Tool usage top 20, event types, agent types |
| `GET /api/pricing` | Model pricing rules for cost comparison |
### Workflow Intelligence API (`GET /api/workflows/{sessionId}`)
Returns these 11 datasets per session:
| Dataset | Content |
|---------|---------|
| `stats` | Aggregate session stats: tool count, agent depth, event count |
| `orchestration` | **DAG**: agent nodes with parent/child edges, depths, types |
| `toolFlow` | **Transition matrix**: tool A → tool B with counts (common sequences) |
| `effectiveness` | **Subagent success**: per-type completion rates, avg duration, task success |
| `patterns` | **Recurring sequences**: detected workflow patterns with frequency |
| `modelDelegation` | **Model choices**: which models are delegated which tasks |
| `errorPropagation` | **Error flow by depth**: where in the agent tree errors originate and propagate |
| `concurrency` | **Concurrency lanes**: overlapping agent execution timelines |
| `complexity` | **Complexity score**: numerical score based on depth, breadth, tool diversity |
| `compaction` | **Compaction impact**: token savings, frequency, context health |
| `cooccurrence` | **Agent pairs**: which agents frequently run together |
## Optimization Analyses
### 1. Tool Flow Optimization
From `toolFlow` transition data:
- Identify the most common tool sequences (e.g., Read → Edit → Bash)
- Find redundant transitions (same tool called repeatedly = retries)
- Detect anti-patterns: high-frequency failure loops
- Recommend tool chain shortcuts
### 2. Subagent Strategy
From `effectiveness` + `orchestration`:
- Which subagent types (task, explore, code-review) have highest completion rates
- Average duration per subagent type — are subagents taking too long?
- Underutilized types: tasks that could benefit from delegation
- Over-spawning: too many subagents for simple tasks
### 3. Model Delegation Analysis
From `modelDelegation`:
- Which models handle which task types
- Cost-per-task comparison across models
- Opportunities to delegate simple tasks to cheaper models (Haiku/Sonnet instead of Opus)
- Calculate estimated savings from model rebalancing
### 4. Error Prevention
From `errorPropagation`:
- Where errors originate (agent depth level)
- How errors cascade to parent agents
- Error types (APIError, tool failure) by frequency
- Defensive strategies: which patterns lead to fewer errors
### 5. Concurrency Optimization
From `concurrency`:
- Which agents run in parallel vs sequential
- Bottlenecks: sequential agents that could be parallelized
- Resource contention: overlapping heavy tasks
### 6. Context Health
From `compaction`:
- How often compaction occurs per session
- Token recovery from compaction baselines
- Sessions that hit context limits — suggest breaking into smaller tasks
## Output
Prioritized recommendations table:
| # | Recommendation | Source Data | Impact | Effort | Est. Savings |
|---|---------------|-------------|--------|--------|-------------|
Top 5 recommendations with detailed explanation, supporting data from the workflow API, and implementation steps.Excerpt, first 3,986 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 1f059c4
git clone https://github.com/hoangsonww/Claude-Code-Agent-Monitor git -C Claude-Code-Agent-Monitor checkout 1f059c400d07
The author documents no install command, so this uses the repository directly. Our verdict covers commit 1f059c400d07 only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Claude Code | Mentioned in its text, not tested | Skills for Claude Code · About Claude Code |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
1f059c400d07
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/hoangsonww/workflow-optimizer/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All automation skills →hoangsonww/Claude-Code-Agent-Monitor
Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps,…
hoangsonww/Claude-Code-Agent-Monitor
Break down Claude Code costs using the Agent Monitor pricing engine. Shows per-model costs (input, output, cache_read, cache_write at $/Mtok rates), per-session costs, daily trends, and compaction baseline token…
hoangsonww/Claude-Code-Agent-Monitor
Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity…
hoangsonww/Claude-Code-Agent-Monitor
Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by…
hoangsonww/Claude-Code-Agent-Monitor
Export Claude Code session and analytics data in JSON, CSV, or Markdown formats. Supports exporting sessions, events, costs, and analytics for external analysis or reporting. Use for data backup or integration.
hoangsonww/Claude-Code-Agent-Monitor
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Add this badge to your README
[](https://modelsatlas.com/skills/hoangsonww/workflow-optimizer/)
<a href="https://modelsatlas.com/skills/hoangsonww/workflow-optimizer/"><img src="https://modelsatlas.com/skills/hoangsonww/workflow-optimizer/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Workflow Optimizer
What does the Workflow Optimizer skill do?
Is Workflow Optimizer safe to install?
What can Workflow Optimizer access on my machine?
Which assistants does Workflow Optimizer work with?
How current is this page?
Sources
- github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plug — the audited source at commit 1f059c400d07 and every finding aboveObserved · 16 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Workflow Optimizer skill do?
- Is Workflow Optimizer safe to install?
- What can Workflow Optimizer access on my machine?