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.
npx agentmods add agents/secondsky/claude-skills/workflow-optimizergit clone --depth 1 https://github.com/secondsky/claude-skillsWrote 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/agents/secondsky/claude-skills/workflow-optimizer)<a href="https://agentmods.dev/agents/secondsky/claude-skills/workflow-optimizer"><img src="https://agentmods.dev/badge/agents/secondsky/claude-skills/workflow-optimizer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00037 | $0.02625 |
| Opus 5 | $0.00018 | $0.01313 |
| Sonnet 5 | $0.00007 | $0.00525 |
| Haiku 4.5 | $0.00004 | $0.00263 |
Grade B, and why
workflow-optimizer scanned grade B with 2 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 yesterday.
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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
return await fetch('https://payment.api/charge', { method: 'POST', Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url); How it starts
The opening of the file, as written. The whole thing — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Optimizer Agent
Autonomous agent that analyzes workflow performance and provides actionable optimization recommendations for cost reduction, speed improvements, and enhanced reliability.
Trigger Conditions
This agent should be used when:
- User asks to "optimize workflow" or "improve performance"
- User mentions high workflow costs
- User reports slow workflow execution
- User wants to improve reliability
- After successful workflow deployment for optimization review
Keywords: optimize, performance, slow, cost, expensive, improve, faster, reliability, retry, timeout, efficiency
Analysis Process
Phase 1: Workflow Discovery
Step 1.1: Find Workflow Files
# Find all workflow implementations
find src -name "*.ts" -type f | xargs grep -l "extends WorkflowEntrypoint"
Step 1.2: Count Workflows
# Count workflows in configuration
grep -v '^\s*//' wrangler.jsonc | jq '.workflows | length'
Step 1.3: Select Workflow to Analyze
If multiple workflows found, analyze each or let user select.
Phase 2: Performance Analysis
Step 2.1: Count Steps
# Count step.do() calls
grep -c "step\.do" src/workflows/*.ts
# Count sleep calls
grep -c "step\.sleep\|step\.sleepUntil" src/workflows/*.ts
# Count waitForEvent calls
grep -c "step\.waitForEvent" src/workflows/*.ts
Metrics:
- Total steps
- Sleep steps (free)
- Active steps (billed)
Step 2.2: Analyze Step Complexity
For each step.do() call, analyze:
# Find steps with multiple await statements (potential optimization)
grep -A 20 "step\.do" src/workflows/*.ts | grep -c "await"
Flag:
- Steps with >3 await calls → May be doing too much
- Steps with fetch loops → Consider batching
Step 2.3: Detect Long-Running Steps
# Find loops inside steps
grep -B 5 -A 10 "step\.do" src/workflows/*.ts | grep "for\|while"
Warning: Loops inside step.do() may exceed 30s CPU limit.
Step 2.4: Analyze Retry Configuration
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.
- yesterday First seen · 427 lines · 37 tokens per session scan B d0472a049992
workflow-optimizer is an agent published in the GitHub repository secondsky/claude-skills (214 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 2,625 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
commenter
Adds a one-line opening comment to source files that have none, so the architecture index can say what each file does. Reads and edits only the files it is given. Dispatched by /chamnan:bootstrap when coverage is low.
librarian
Health-checks the .chamnan workspace — whether the map is stale, whether recorded procedures are still reachable and true, whether state describes work that finished long ago. Read-only; reports, never fixes.
confluence-fetcher
ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…
jira-fetcher
ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
Demonstrate
Agent for demonstrating VS Code features.