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 skills add nickstellarstreamai/ai-opportunity-finder --skill workflow-auditgit clone --depth 1 https://github.com/nickstellarstreamai/ai-opportunity-finderWrote 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/nickstellarstreamai/ai-opportunity-finder/workflow-audit)<a href="https://agentmods.dev/skills/nickstellarstreamai/ai-opportunity-finder/workflow-audit"><img src="https://agentmods.dev/badge/skills/nickstellarstreamai/ai-opportunity-finder/workflow-audit/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/nickstellarstreamai/ai-opportunity-finder/workflow-audit"><img src="https://agentmods.dev/badge/skills/nickstellarstreamai/ai-opportunity-finder/workflow-audit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.01587 |
| Opus 5 | $0.00032 | $0.00794 |
| Sonnet 5 | $0.00013 | $0.00317 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
workflow-audit 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Audit
Guides you through a structured audit of a specific workflow or business process to identify exactly where AI and automation could save time, reduce errors, or improve quality. This turns the abstract ("find AI opportunities") into the concrete ("here's where 15 hours/week is being wasted").
How It Works
I'll walk you through a series of questions about how a specific process works today. You describe the reality — I map the workflow, flag the pain points, and score the automation opportunities.
This is an interactive skill. I'll ask questions in phases, then produce a structured audit report.
What I Need From You
To start, provide:
- Department or function (e.g., "Sales", "Operations", "Finance", "HR")
- The specific process to audit (e.g., "monthly reporting", "customer onboarding", "invoice processing")
- Who's involved (roles, not necessarily names)
I'll then ask follow-up questions in three phases.
The Audit Process
Phase 1: Process Mapping (5-10 questions)
I'll ask you to walk me through the process step by step:
- "What triggers this process? How does it start?"
- "What happens next? Who does what?"
- "What tools or systems are used at each step?"
- "Where does information get passed between people?"
- "How does this process end? What's the final output?"
Goal: Map the actual workflow as it exists today — not the org chart version, but how it really works.
Phase 2: Pain Point Identification (5-8 questions)
Now I'll probe for problems:
- "Which step takes the most time?"
- "Where do errors or rework happen most often?"
- "What's the most frustrating part of this process?"
- "Are there any workarounds people use to get around the official process?"
- "What happens when [key person] is out sick or on vacation?"
- "How many hours per week/month does this process consume?"
Goal: Quantify the pain. Get specific numbers — hours, frequency, error rates.
Phase 3: Automation Assessment (3-5 questions)
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.
- 12d ago First seen · 182 lines · 63 tokens per session scan A 15de04777c8e
workflow-audit is a skill published in the GitHub repository nickstellarstreamai/ai-opportunity-finder (11 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,587 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…