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 saolalab/clawforce --skill process-improvementgit clone --depth 1 https://github.com/saolalab/clawforceWrote 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/saolalab/clawforce/process-improvement)<a href="https://agentmods.dev/skills/saolalab/clawforce/process-improvement"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/process-improvement/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/saolalab/clawforce/process-improvement"><img src="https://agentmods.dev/badge/skills/saolalab/clawforce/process-improvement.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.00020 | $0.00360 |
| Opus 5.5 | $0.00008 | $0.00144 |
| Sonnet 5.5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
process-improvement 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.
What it actually says
Process Improvement
Process Mapping
Notation (BPMN Simplified)
- ○ Start/End event
- □ Task/Activity
- ◇ Decision gateway
- → Flow direction
Levels of Detail
- L1: High-level process areas
- L2: Sub-processes
- L3: Detailed activities
- L4: Work instructions
Analysis Techniques
Value Stream Mapping
- Identify value-adding vs non-value-adding steps
- Calculate cycle time vs wait time
- Find bottlenecks
Root Cause Analysis
- Define the problem
- Collect data
- Identify possible causes (5 Whys)
- Verify root cause
- Implement solution
Improvement Framework (DMAIC)
| Phase | Activities |
|---|---|
| Define | Problem statement, scope, goals |
| Measure | Current state, baseline metrics |
| Analyze | Root causes, opportunities |
| Improve | Solutions, pilot, implement |
| Control | Sustain, monitor, document |
Process Documentation Template
## Process: [Name]
### Purpose
Why this process exists
### Trigger
What starts this process
### Inputs
What is needed to start
### Steps
1. Step one
2. Step two
3. Decision point
- If yes: Step 3a
- If no: Step 3b
### Outputs
What this process produces
### Metrics
How we measure success
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 First seen · 74 lines · 20 tokens per session scan A 3b2f4ff4e632
process-improvement is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 360 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-30.
Other skills, from other repositories
03_task6
A workflow for collecting Slack messages from different departments and preparing a board-level execution-summary draft for an executive.
03_task4
Reads recent Slack messages to compile an accurate project status report and saves it as a draft for review before sending to a client. Use when: preparing a client-facing update, reconciling conflicting or revised numbers from multiple sources, or drafting a message that requires human review before sending.
03_task5
Triages a support inbox, prioritizes urgent issues, routes each to the right internal team member, and drafts any customer-facing replies for review. Use when: catching up on a backlog of support messages, producing an escalation report, or routing issues to appropriate owners.
03_task2
Extracts action items and pending tasks from Slack messages. Use when: reviewing unread messages for todos, finding deadlines or requests directed at the user, or producing a task summary from recent Slack activity.
03_task1
Coordinates meeting scheduling via Gmail and Calendar APIs. Use when: scheduling a meeting, checking participant availability, sending coordination emails, creating calendar events, or notifying organizers of confirmed bookings.
meeting-to-action
Convert meeting notes or transcripts into clear summaries, decisions, and action items with owners and due dates. Use when a user asks to turn a meeting recording, transcript, or notes into a follow-up plan.