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 run-operational-reviewgit 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/run-operational-review)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-operational-review"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-operational-review/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/run-operational-review"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-operational-review.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.00026 | $0.01209 |
| Opus 5 | $0.00013 | $0.00605 |
| Sonnet 5 | $0.00005 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
run-operational-review 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 7d 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.
Run Operational Review
Facilitate a structured operational review meeting that surfaces performance issues, drives accountability, and aligns leadership on corrective actions.
Why This Is Best Practice
Adopted by: Amazon (weekly S-Team reviews), Google (quarterly OKR reviews), and scaling companies using Harnish's "Scaling Up" rhythm methodology Impact: Amazon's S-Team review process, described in "Working Backwards" (Bryar & Carr, 2021), is credited with maintaining operational discipline across 1M+ employees. Google's quarterly OKR reviews increased cross-team alignment by 40% in the 2012–2016 period. Harnish documents that companies running weekly, monthly, and quarterly cadenced reviews grow 2x faster than those with ad-hoc review processes. Why best: Without a structured review rhythm, problems compound silently, accountability diffuses, and leadership operates on anecdote rather than data. Operational reviews are the organizational immune system that detects and responds to execution failures.
Sources: Bryar & Carr "Working Backwards" (2021) — Amazon S-Team review; Google re:Work OKR methodology; Harnish "Scaling Up: How a Few Companies Make It...and Why the Rest Don't" (2014)
Steps
-
Define the review cadence — establish a three-level rhythm: daily standups (15 min, teams), weekly operational reviews (60 min, functional leaders), monthly business reviews (90 min, senior leadership), and quarterly strategic reviews (half-day, executives). Each level has different content and attendees.
-
Set the agenda template — standardize the agenda so attendees know what to expect: (1) KPI scorecard review, (2) red metric deep-dives, (3) key decisions required, (4) cross-functional blockers, (5) upcoming milestone review. No agenda item without an owner.
-
Require pre-read distribution 24 hours in advance — following Amazon's "no PowerPoint" model: distribute a written narrative or data package 24 hours before the meeting. Meeting time is for discussion and decisions, not data presentation.
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.
- 7d ago First seen · 63 lines · 26 tokens per session scan A 007409c9518b
run-operational-review is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 22d ago), licensed MIT. It adds 26 tokens to every session and 1,209 once invoked, about $0.0001 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
org-report
Generate an executive organization brief (leadership chain, direct reports, extended teams, and vendor partners) for a target person. Produces a Word + PDF report from a directory MCP source (WorkIQ is the reference implementation) and displays it in a Copilot canvas. Triggers on "generate org report for X", "build…
coaching-techniques
GROW model, active listening, developmental feedback, and team growth approaches.
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
stakeholder-management
Influence mapping, communication strategies, and expectation management for complex organizations.
scaffolding-generator
Pattern-aware code scaffolding that detects existing conventions and generates new components matching the codebase style. Use when asked to "scaffold a component", "generate boilerplate", "create a new module", "bootstrap a service", "add a new endpoint", "create a new controller", or "add a new feature module".…
status-reporting
Create stakeholder-friendly project status updates and progress reports.