audit-process-efficiency

audit-process-efficiency is a skill for Claude Code from jeffreytse/grimoire-core. It costs 25 tokens per session (960 once invoked), scanned A, original, MIT.

A structured review of a repeatable workflow to find wasted effort, delays, and bottlenecks. It follows work from its starting event to its completed outcome and maps each step.

In plain words
What is it for?
Auditing workflows such as support tickets, documents, orders, or other business processes and identifying practical efficiency improvements.
Why use it?
People inside a process often overlook wasted time and avoidable handoffs, while a mapped review turns those problems into a prioritized improvement list.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 156 skills shipped together

Good fit Auditing workflows such as support tickets, documents, orders, or other business processes and identifying practical efficiency improvements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/audit-process-efficiency
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill audit-process-efficiency
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 156 skills.

Wrote 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.

agentmods badge for audit-process-efficiency

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/audit-process-efficiency/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/audit-process-efficiency)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/audit-process-efficiency"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/audit-process-efficiency/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.

agentmods 80×15 button for audit-process-efficiency

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/audit-process-efficiency"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/audit-process-efficiency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 960 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00960
Opus 5.5 $0.00010 $0.00384
Sonnet 5.5 $0.00005 $0.00192
Haiku 4.5 $0.00003 $0.00096

Measured 1mo ago against content hash 5cd46512b5e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

audit-process-efficiency 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.

skills/business/operations/skills/audit-process-efficiency/SKILL.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Audit Process Efficiency

Systematically identify waste and bottlenecks in a workflow using lean value stream mapping techniques.

Why This Is Best Practice

Adopted by: Toyota, Amazon operations, General Electric Six Sigma programs, NHS Lean transformation Impact: Value stream mapping studies show 30–50% lead-time reduction in manufacturing and 20–40% in knowledge-work processes when waste is systematically eliminated (Lean Enterprise Institute, 2021)

Why best: Most process inefficiency is invisible to participants because they are inside it. A structured audit externalizes the process, quantifies non-value-adding time, and produces a prioritized improvement backlog rather than a list of complaints.

Steps

  1. Define the scope — Choose one process with a clear start event and end outcome. Example: "customer submits support ticket → ticket resolved and closed." Do not audit everything at once.
  2. Walk the process — Follow one unit of work (a ticket, a document, an order) through every step from start to finish. Observe in person or via screen share; do not rely on documented procedures alone.
  3. Map the current state — Draw each step as a box. Between boxes, record: wait time, queue depth, and who hands off to whom. Include decision points (if/else branches). Use sticky notes or a digital canvas.
  4. Classify each step — Label every step: Value-Adding (VA) = customer would pay for it; Business Non-Value-Adding (BNVA) = necessary but wasteful (compliance, approvals); Non-Value-Adding (NVA) = pure waste to eliminate.
  5. Calculate the efficiency ratio — Total VA time ÷ Total lead time. A ratio below 20% is common in knowledge work and signals major improvement opportunity.
  6. Identify the constraint — Find the step with the longest cycle time or largest queue. Per Theory of Constraints, improving any step except the constraint does not improve throughput.
  7. Design the future state — Redesign the process to eliminate NVA steps, reduce handoffs, and unblock the constraint. Aim for a 25–50% reduction in lead time. Document the future state map alongside the current state.
  8. Build the improvement backlog — Convert each change into a concrete action item: owner, due date, success metric. Prioritize by impact on the constraint.

Read the full file on GitHub · 56 lines

Changes

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.

  1. 1mo ago First seen · 56 lines · 25 tokens per session scan A 5cd46512b5e8

Subscribe to this mod's changes

audit-process-efficiency is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 960 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-09-03.