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 fatihguner/foreman --skill kaizen-bprgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/kaizen-bpr)<a href="https://agentmods.dev/skills/fatihguner/foreman/kaizen-bpr"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/kaizen-bpr/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/fatihguner/foreman/kaizen-bpr"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/kaizen-bpr.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.00088 | $0.03278 |
| Opus 5 | $0.00044 | $0.01639 |
| Sonnet 5 | $0.00018 | $0.00656 |
| Haiku 4.5 | $0.00009 | $0.00328 |
Grade A, and why
kaizen-bpr 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 5d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Kaizen & Business Process Reengineering
Two philosophies of improvement emerged from opposite ends of the industrial world, and they could hardly be more different in temperament. From Japan: Kaizen -- the quiet, relentless discipline of making things a little better every day. From America: Business Process Reengineering (BPR) -- the dramatic act of tearing up existing processes and rebuilding them from scratch. One whispers. The other shouts. Toyota embodied the first; Michael Hammer and James Champy evangelised the second in their 1993 manifesto Reengineering the Corporation. The genius lies not in choosing between them but in understanding when each is appropriate -- and recognising that most organisations need both, applied at different times and to different problems.
The Framework
Kaizen: The Continuous Improvement Philosophy
Kaizen (Japanese: "change for better") is not a technique but a culture. Masaaki Imai introduced it to Western audiences in 1986, describing the management philosophy that powered Japan's post-war industrial ascent. The core principle is disarmingly simple: every process can be improved, every day, by the people who do the work.
Before Kaizen:
- Improvement is a management responsibility
- Changes come in large, infrequent projects
- Workers execute; managers think
- Defects are found at inspection
- "Good enough" is the standard
After Kaizen:
- Improvement is everyone's responsibility
- Changes come in small, continuous increments
- Workers observe, suggest, and implement improvements
- Defects are prevented at the source
- "Better than yesterday" is the standard
The Kaizen Cycle (PDCA):
- Plan -- Identify a specific, measurable improvement opportunity. Define the current state and the target state.
- Do -- Implement the change on a small scale. Treat it as an experiment, not a commitment.
- Check -- Measure the results. Did the change achieve the target? What unexpected effects emerged?
- Act -- If successful, standardise the new method. If not, analyse why and begin the cycle again.
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.
- 5d ago First seen · 220 lines · 88 tokens per session scan A 4275f8aa56ba
kaizen-bpr is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 5d ago), licensed MIT. It adds 88 tokens to every session and 3,278 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-09-06.
Other skills, from other repositories
manage-taskboard
Manage Codex Taskboard / e-taskboard work with taskctl. Use for taskboard issue IDs, status sync, comments, or taskctl cloud setup—not for unrelated product docs.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
fly
Fly one thought to its destination across concurrent agents, on whatever the project and harness already have. Lands only when the user has accounted for every detail, never on an agent's say-so.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
quality-management-expert
Build comprehensive quality management solutions including QMS implementation, audit tracking, nonconformance management, and continuous improvement programs. Use when the user mentions a QMS, ISO 9001, audits and CAPA, nonconformance tracking, Six Sigma, or continuous improvement programs.
plan-to-issues
A tool that turns an agreed work plan into linked GitHub issues, with one larger parent issue and smaller task issues beneath it.