Borrowing it
Nothing to install: this file belongs to katopz/katgpt-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/katopz/katgpt-rs/develop/.agents/skills/feature-gate-audit/SKILL.mdgit clone --depth 1 https://github.com/katopz/katgpt-rsWrote 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/katopz/katgpt-rs/feature-gate-audit)<a href="https://agentmods.dev/skills/katopz/katgpt-rs/feature-gate-audit"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/feature-gate-audit/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/katopz/katgpt-rs/feature-gate-audit"><img src="https://agentmods.dev/badge/skills/katopz/katgpt-rs/feature-gate-audit.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.00228 | $0.06717 |
| Opus 5.5 | $0.00091 | $0.02687 |
| Sonnet 5.5 | $0.00046 | $0.01343 |
| Haiku 4.5 | $0.00023 | $0.00672 |
Grade A, and why
feature-gate-audit 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 1mo 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
feature-gate-audit — Verify feature-gate claims against production code
This skill exists because of a caught error chain: session f92a7ffe in
riir-ai (2026-07-18) framed npc_sleep_time's engine-DEFAULT-ON /
civ-OPT-IN state as a "promotion discrepancy" and claimed the catalog
was "wired but not yet exercised in production civ tick". Session
f865913e (same day) verified both claims against production code and
found them factually wrong:
- The split is a deliberate layer split (engine = generic runtime;
civ = IP-bearing catalog + graceful-degradation hook into
SleepConsolidateNode::tickGate 3). - The catalog IS exercised in production via
crates/riir-games-civ/src/civ/daily_loop/mod.rs:1071-1078, which callsctx.sleep_runtime.sleep_cycle_tick(&hla, &self.dirs).
The three defenses below would have caught both errors before they landed. Apply them to every feature-gate claim you encounter.
When to use
- A doc, plan, issue, commit message, or session summary claims a "promotion discrepancy" between two crates' feature-gate status
- A doc claims a feature is "wired but not yet exercised in production"
- You encounter a
// Default-off until G1–GN GOAT gate passescomment in source code - Before promoting a feature flag to default-on (or demoting to opt-in)
in any product-set repo (7; canonical list in
katgpt-rs/AGENTS.md§"Repo count" — read the LIST, not the count: this cell said 7-omittingriir-dapps, then 8-counting-retired-riir-armageddon. A count that drifts from the canonical list is the exact defect this skill audits in others) - Quarterly as a feature-gate-hygiene gate (alongside
doc-syncandgoat-audit)
The four defenses
Defense 1 — Verify every "discrepancy" / "not yet wired" claim against production code
NEVER propagate a doc/plan/session-summary's framing of feature-gate state without first grepping the actual production wiring. Plausible-but- wrong framings are the canonical failure mode — they read as reasoned verdicts, get propagated through summaries, and solidify into "facts" that downstream sessions trust.
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.
- 1mo ago Changed 04afa670ef85
- 1mo ago Changed · +2 lines e1ef46f0f88f
- 1mo ago Changed · +7 lines 772a99c4be46
- 2mo ago First seen · 360 lines · 228 tokens per session scan A 01e7f518337c
feature-gate-audit is a skill published in the GitHub repository katopz/katgpt-rs (140 stars, last pushed today), licensed MIT. It adds 228 tokens to every session and 6,717 once invoked, about $0.0009 per session on Opus 5.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-08-30.
Other skills, from other repositories
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…