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 Lingtai-AI/lingtai --skill availability-save-gategit clone --depth 1 https://github.com/Lingtai-AI/lingtaiWrote 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/lingtai-ai/lingtai/availability-save-gate)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/availability-save-gate"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/availability-save-gate/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/lingtai-ai/lingtai/availability-save-gate"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/availability-save-gate.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.00044 | $0.00526 |
| Opus 5 | $0.00022 | $0.00263 |
| Sonnet 5 | $0.00009 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
preset-skill-op-availability-save-gate 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 9d 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.
What it actually says
Availability / save gate
Evidence: tui/internal/tui/preset_editor.go's commit().
Save is structural-only
commit() runs the preset's structural Validate() and, if it passes,
saves immediately. There is no live HTTP call, no pending/checking state,
and no per-tuple credential fingerprinting gate on Save — for any
provider, including Codex, Codex-pool, and API-key providers like
DeepSeek. See reference/operations/saved-presets/SKILL.md for what
Validate() checks.
History
An earlier revision of this editor ran a real live provider/model call on every Save and hard-blocked the save on a non-2xx response (a "real-availability gate"). That gate false-positived broadly — every provider, including working Codex and API-key configurations, could be rejected by transient network/provider conditions unrelated to whether the configuration was actually usable — and was removed (2026-07-23, reported by Jason). It has not been replaced by another probe, whitelist, or retry loop.
Where live availability diagnosis actually lives
/doctor (tui/internal/tui/doctor.go's probeLLM) and real runtime
execution remain the places that diagnose whether a provider/model is
actually reachable. Save does not duplicate that check.
Operations
For structural Validate() and the Load/Save/Delete file contract, see
reference/operations/saved-presets/SKILL.md. For what happens after a
successful save — activation and /refresh — see
reference/operations/activation-session-refresh/SKILL.md.
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.
- 9d ago First seen · 50 lines · 44 tokens per session scan A 45c215f3a6c4
preset-skill-op-availability-save-gate is a skill published in the GitHub repository Lingtai-AI/lingtai (700 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 526 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…