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 agentmods add skills/hoavdc/codexkit/codexkit-sandop-facilitatornpx skills add hoavdc/CodexKit --skill codexkit-sandop-facilitatorgit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-sandop-facilitator)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-sandop-facilitator"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-sandop-facilitator.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.00705 |
| Opus 5 | $0.00041 | $0.00352 |
| Sonnet 5 | $0.00016 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
codexkit-sandop-facilitator 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 yesterday.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
S&OP Facilitator
Purpose
Create the structure and decision flow needed for an effective monthly S&OP cycle.
When to use
- A business needs a repeatable monthly S&OP rhythm.
- Demand and supply views are not reconciling cleanly.
- Executives need a short pack of tradeoffs and decisions.
When not to use
- The request is limited to one SKU reorder calculation.
- No demand, supply, inventory, or capacity context is available.
Inputs
- demand view, forecast assumptions, and commercial changes
- supply constraints, lead times, and capacity view
- inventory health, backlog, and service-level targets
- open tradeoffs that need executive decisions
Procedure
- Separate the cycle into demand review, supply review, reconciliation, and executive review.
- Normalize the numbers and assumptions across functions.
- Surface the biggest mismatches in volume, mix, timing, capacity, and inventory.
- Quantify tradeoffs where possible: service, cost, cash, and risk.
- Write the few decisions executives actually need to make.
- End with owners, dates, and decision follow-through.
Output
- monthly S&OP cycle plan
- demand and supply tension summary
- reconciliation view with tradeoffs
- executive decision sheet
- follow-up actions and owners
Definition of done
- The cycle has a clear meeting sequence and purpose.
- Tradeoffs are explicit across service, cost, cash, and risk.
- Decision owners and follow-through are visible.
Examples
- "Build this month's S&OP executive pack from our demand, supply, and inventory notes."
- "Facilitate a pre-S&OP reconciliation for these conflicting forecast and capacity inputs."
Quality Criteria
- Steps are executable in sequence without external context
- Decision points have clear if/then branching
- Rollback or abort procedures are documented for risky steps
- Expected duration or time-per-step is estimated
Verification (4C)
| Check | Question |
|---|---|
| Correctness | Do the steps execute correctly in the order specified? |
| Completeness | Are decision points, error handling, and escalation paths all documented? |
| Context-fit | Could someone with the right access but no prior context complete this runbook? |
| Consequence | If Step N fails and the operator skips to Step N+1, what breaks? |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 85 lines · 82 tokens per session scan A 132f8a283e55
codexkit-sandop-facilitator is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 82 tokens to every session and 705 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
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
product-reviews
Help users design and facilitate product reviews that shift from status updates to strategic deep-dives, ensuring high-quality craftsmanship and organizational alignment.
delivering-delegated-linear-issues
当用户明确要求领取、处理、批量清空或定时扫描 Linear 的 Delegated to Agent issue 时使用；按队列状态、领取竞争、交付路径和收尾四个阶段渐进读取。.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.