Borrowing it
Nothing to install: this file belongs to Smart-AI-Memory/attune-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Smart-AI-Memory/attune-ai/main/.agents/skills/workflow-orchestration/SKILL.mdgit clone --depth 1 https://github.com/Smart-AI-Memory/attune-aiWrote 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/skills/smart-ai-memory/attune-ai/workflow-orchestration)<a href="https://agentmods.dev/skills/smart-ai-memory/attune-ai/workflow-orchestration"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/workflow-orchestration/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.
<a href="https://agentmods.dev/skills/smart-ai-memory/attune-ai/workflow-orchestration"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/workflow-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00034 | $0.00830 |
| Opus 5.5 | $0.00014 | $0.00332 |
| Sonnet 5.5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
workflow-orchestration 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Orchestration
IMPORTANT: Start your response with a context preamble.
Call help_lookup(topic="workflows", mode="preamble") and
display the returned preamble text as a blockquote. Then
tell the user they can say "tell me more" for a step-by-step
guide, or answer the scoping questions below to proceed.
If the MCP call fails, fall back to:
Workflow Orchestration — Runs multiple analysis workflows in sequence and combines the results.
Scoping
Before running, ask:
- Goal: "What are you trying to accomplish?"
- Scope: "Which path or files should I analyze?"
Based on the answer, route to the appropriate workflow.
Workflows
Analysis
| Workflow | MCP Tool | What It Does |
|---|---|---|
| Security Audit | security_audit |
Scans for vulnerabilities, dangerous patterns, secrets |
| Code Review | code_review |
Quality, correctness, and security analysis |
| Bug Prediction | bug_predict |
Pattern analysis and likely bug detection |
| Performance Audit | performance_audit |
Bottleneck detection and optimization |
| Deep Review | deep_review |
Multi-pass: security, quality, and test gap analysis |
Testing
| Workflow | MCP Tool | What It Does |
|---|---|---|
| Test Generation | test_generation |
Generates unit tests with edge cases |
| Test Audit | test_audit |
Coverage audit and gap detection |
| Parallel Test Gen | test_gen_parallel |
Batch test generation for 10-50 modules |
Documentation
| Workflow | MCP Tool | What It Does |
|---|---|---|
| Doc Audit | doc_audit |
Documentation freshness and gap analysis |
| Doc Generation | doc_gen |
Generate documentation for a module |
| Doc Orchestrator | doc_orchestrator |
Full documentation maintenance pipeline |
Release
| Workflow | MCP Tool | What It Does |
|---|---|---|
| Release Notes | release_notes |
Changelog draft + go/no-go advisory |
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.
- 1mo ago Changed · +15 lines 04a2f91cdb4c
- 1mo ago First seen · 98 lines · 34 tokens per session scan A ba78c230b900
workflow-orchestration is a skill published in the GitHub repository Smart-AI-Memory/attune-ai (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 830 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
ripple
Analyzing pre-change impact across vertical (dependency chains, files) and horizontal (pattern consistency, naming) dimensions. Use to estimate blast radius before a refactor. No code.
sweep
Detecting unnecessary files, unused code, and orphaned files, and proposing safe deletion. Not for removal execution (Builder), repo structure (Grove), or scope cutting (Void).
bolt
Optimizing frontend (re-render, memoization, lazy loading) and backend (N+1, indexing, caching, async) performance, plus continuous auto-tuning loops for GC/threadpool/cache/worker settings.
lens
Comprehending and investigating codebases: structure mapping, feature discovery, data flow tracing for 'does X exist?' or 'how does Y work?'. Includes a conversational ask mode. Does not write code.
scout
Investigating bugs via root cause analysis, reproduction steps, and impact assessment. Investigation-only — finds why bugs occur and where to fix them, no code. Use when a bug needs RCA before a fix.
trail
Investigating git history, analyzing regression root causes, and performing code archaeology. Time-travels through commits to uncover truth. Use for git history investigation.