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 event4u-app/agent-config --skill operational-readinessgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/operational-readiness)<a href="https://agentmods.dev/skills/event4u-app/agent-config/operational-readiness"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/operational-readiness/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/event4u-app/agent-config/operational-readiness"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/operational-readiness.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.00046 | $0.01915 |
| Opus 5 | $0.00023 | $0.00958 |
| Sonnet 5 | $0.00009 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
operational-readiness 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 8d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
operational-readiness
When to use
Use when turning evidence that already exists into a verdict: is this system ready to operate. The inputs come from other skills; this one adjudicates them and refuses to average.
Do NOT use when:
- Producing the observability evidence itself (use
logging-monitoring) - Deciding what earns a page (use
alerting-doctrine) - Hardening the host (use
server-hardening) - Working through a release checklist and rollout plan (use
launch-readiness— that is a pre-merge procedure; this is a verdict over operational evidence) - Running an incident already in progress (use
incident-commander)
The verdict is an enum with a floor
ONE RED MAKES THE VERDICT not-ready, WHATEVER SITS BESIDE IT.
UNKNOWN IS NEVER GREEN. THERE IS NO SCORE, NO WEIGHT, NO AVERAGE.
| Verdict | Condition |
|---|---|
ready |
Every input is green. No reds, no unknowns. |
ready-with-risk |
Every input is green or amber, at least one amber, no reds and no unknowns. Each amber names its accepted risk and an owner. |
not-ready |
At least one red — or at least one unknown. |
Three properties, each load-bearing:
- The floor is absolute. One red among nineteen greens is
not-ready. The red is the interesting input precisely because the greens cannot answer it. unknownlands innot-ready, not inready-with-risk. An uninspected input is not a small risk, it is an unmeasured one, and treating it as amber is how "we never checked" becomes "we accepted it". Amber requires someone to have looked and named what they are accepting.- There is no numeric path. No readiness percentage, no weighted score, no count of greens, no "N of M passing". Any such construct can hide a red, which is the only failure mode this skill exists to prevent. If you catch yourself producing a number, the verdict has already been lost.
Typed evidence intake
Each input arrives from an owning surface and keeps its provenance. This skill does not re-derive an input — it reads the verdict the owner produced.
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.
- 8d ago First seen · 185 lines · 46 tokens per session scan A 83972d87b80f
operational-readiness is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 1,915 once invoked, about $0.0002 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-04.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.