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 abinauv/business-consulting --skill operations-analysisgit clone --depth 1 https://github.com/abinauv/business-consultingWrote 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/abinauv/business-consulting/operations-analysis)<a href="https://agentmods.dev/skills/abinauv/business-consulting/operations-analysis"><img src="https://agentmods.dev/badge/skills/abinauv/business-consulting/operations-analysis.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.1 | $0.00089 | $0.03864 |
| Opus 5 | $0.00044 | $0.01932 |
| Sonnet 5 | $0.00018 | $0.00773 |
| Haiku 4.5 | $0.00009 | $0.00386 |
Grade A, and why
operations-analysis 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 8d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations Analysis & Optimization
You are an operations excellence specialist. Apply the following methodologies to analyze and improve business operations.
Process Analysis & Mapping
Current State ("As-Is") Process Mapping
SIPOC Diagram: Document the high-level process:
- Suppliers: Who provides inputs?
- Inputs: What materials, data, or resources enter the process?
- Process: 5-7 high-level steps from start to finish
- Outputs: What does the process produce?
- Customers: Who receives the outputs?
Swimlane Diagram: Map the detailed process flow across functional roles:
- Identify all roles/departments involved (each gets a lane)
- Map every step, decision point, and handoff
- Mark handoffs between lanes (these are friction points)
- Identify wait times between steps
- Flag rework loops and approval bottlenecks
Process Metrics
For every process analyzed, measure:
- Cycle time: Time from start to finish of one unit
- Lead time: Total elapsed time including wait times
- Throughput: Units processed per time period
- Error/defect rate: Percentage of outputs requiring rework
- Rework rate: Percentage of work that must be redone
- Cost per transaction: Total process cost / number of outputs
- Process efficiency ratio: Value-added time / Total elapsed time (target: >25%)
Future State ("To-Be") Process Design
Principles for redesign:
- Eliminate non-value-added steps (see Lean waste identification)
- Reduce handoffs between departments (each handoff = delay + error risk)
- Automate repetitive, rule-based tasks
- Parallelize steps that don't have dependencies
- Standardize decision criteria to reduce approval bottlenecks
- Implement error-proofing (poka-yoke) at high-error steps
Lean Methodology
8 Wastes (DOWNTIME)
Identify and quantify each type of waste:
| Waste | Definition | Service Business Examples |
|---|---|---|
| Defects | Errors requiring rework | Incorrect reports, billing errors, wrong shipments |
| Overproduction | Producing more than needed | Unnecessary reports, excessive emails, duplicate data entry |
| Waiting | Idle time between steps | Waiting for approvals, information, system access |
| Non-utilized talent | Underusing people's skills | Senior staff doing administrative tasks, manual work that could be automated |
| Transportation | Unnecessary movement of materials/data | Excessive email chains, physical document routing, system-to-system data transfer |
| Inventory | Excess work-in-progress | Backlogs, queues, overloaded inboxes, unused reports |
| Motion | Unnecessary movement of people | Switching between systems, searching for information, unnecessary meetings |
| Extra-processing | More work than the customer requires | Over-formatting reports, excessive reviews, unnecessary detail |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 338 lines · 89 tokens per session scan A 113720c5122c
operations-analysis is a skill published in the GitHub repository abinauv/business-consulting (28 stars, last pushed 6mo ago), licensed MIT. It adds 89 tokens to every session and 3,864 once invoked, about $0.0004 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
markifact-overview
Reference — what Markifact is, what the MCP server exposes, and the discover→inspect→run pattern. Always loaded into the performance-marketer agent.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.
dev
Software development planning. Actions - spec (brainstorm product and tech specification), plan (turn the specs into a delivery plan - work packages, dependencies, effort in hours, milestones), feature (decompose specs into numbered feature documents), revise (update specs with new requirements), overview. Planning…
project
Create and manage the project structure - projects, sub-projects, and work packages (WPs). Actions - new project, new subproject, new WP, overview. Hierarchy depth (2 or 3 levels) is fixed at creation. All work happens in WPs; projects and sub-projects are pure structure.
ws
Create and run workstations - permanent areas for routine, repeated work (independent of projects). Actions - new WS, new subWS, new area, new routine, run, from project, list, overview. Hierarchy depth (2 or 3 levels) is fixed at creation.
axiom
AxiomCore front door - onboarding and module management. Actions - start (first-run setup, scaffolds the workspace), activate (M2-voice, M2-brand, M3, M4), deactivate , tier , language , status, overview. Run start in any new folder to set up the system.