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 jeffreytse/grimoire-core --skill apply-5s-methodologygit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/apply-5s-methodology)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-5s-methodology"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-5s-methodology/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/jeffreytse/grimoire-core/apply-5s-methodology"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-5s-methodology.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.00086 | $0.01698 |
| Opus 5 | $0.00043 | $0.00849 |
| Sonnet 5 | $0.00017 | $0.00340 |
| Haiku 4.5 | $0.00009 | $0.00170 |
Grade A, and why
apply-5s-methodology 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 6d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply 5S Methodology
Apply the five sequential steps — sort, set in order, shine, standardize, sustain — in order to any cluttered or inconsistently organized physical or shared digital workspace, because skipping ahead to standardization before actually sorting and organizing produces a workplace that looks disciplined on paper but reverts to clutter within weeks.
Why This Is Best Practice
Why best: 5S's specific contribution is not "keep things tidy" as a vague aspiration — it's a strict sequence where each step depends on the one before it. Standardizing an organization scheme before genuinely removing unneeded items and establishing a real place for everything produces rules documenting a workspace that doesn't actually reflect reality, which decays immediately. The sequence itself — remove what's unneeded, then organize what remains, then clean and inspect, then document the result as a standard, then build the habit and audit discipline to maintain it — is what prevents the common failure of a one-time cleanup effort reverting within weeks.
Hirano, "5 Pillars of the Visual Workplace" (1995), building on Toyota Production System practice: Hirano formalized the five Japanese terms — Seiri (Sort: remove what is not needed), Seiton (Set in Order: arrange what remains so it has an obvious, findable place), Seiso (Shine: clean the workspace and, in the process, inspect for wear or malfunction that cleaning would otherwise hide), Seiketsu (Standardize: document the resulting organization as a visible, repeatable standard), and Shitsuke (Sustain: build the ongoing habit and audit discipline that keeps the first four steps from decaying) — as a specific, ordered methodology rather than a general tidiness principle, directly rooted in Toyota Production System workplace practice.
Adopted by: 5S is standard practice across Lean manufacturing, adopted broadly beyond Toyota across automotive, electronics, and general manufacturing operations, and increasingly applied to non-manufacturing contexts (offices, shared digital file systems, hospital supply rooms) as a general workspace-discipline methodology. Impact: 5S's specific "shine" step is documented in Lean practice as functioning as an inspection mechanism, not just cleaning — the physical act of cleaning equipment routinely surfaces wear, leaks, or malfunction that would otherwise go undetected until failure; more broadly, 5S implementations are widely credited in Lean manufacturing literature with reducing time lost searching for tools or materials and with surfacing safety and quality issues earlier than they would otherwise be found.
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.
- 6d ago First seen · 63 lines · 86 tokens per session scan A e4be7f0de78c
apply-5s-methodology is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 21d ago), licensed MIT. It adds 86 tokens to every session and 1,698 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-03.
Other skills, from other repositories
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
make-skill-template
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
deep-work-optimization
Focus blocks, distraction management, and flow state triggers for cognitively demanding work.
disagreement-protocol
Canonical phrasing for respectful disagreement without capitulation — structural resistance to sycophancy.
opt-in-workspace-writes
Extensions/tools that auto-write to user workspaces without consent.