agentmods.dev

triggers-and-applygates

triggers-and-applygates is a skill for Claude Code from confighub/confighub-skills. It costs 68 tokens per session (4,255 once invoked), scanned A, original, MIT.

A policy tool for ConfigHub that controls whether configuration checks block an apply, show a warning, or require approval. An ApplyGate blocks a change, while an ApplyWarning reports a problem without blocking it.

In plain words
What is it for?
Use it to create or diagnose validation policies, switch checks between blocking and advisory modes, require approval, and inspect warnings or blocked units.
Why use it?
It turns configuration checks from advice into rules that can stop unsafe changes. It also helps explain why a configuration unit cannot be applied.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the confighub-skills plugin — 16 skills, 1 command, 1 hook shipped together

not rated 2repo changed 2d ago A scan 68 tokens original MIT

Good fit Use it to create or diagnose validation policies, switch checks between blocking and advisory modes, require approval, and inspect warnings or blocked units.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/confighub/confighub-skills/triggers-and-applygates
View source ↗ confighub/confighub-skills
Install

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.

Any agent
npx skills add confighub/confighub-skills --skill triggers-and-applygates
Clone the repo
git clone --depth 1 https://github.com/confighub/confighub-skills

Made for: Claude Code.

Or install confighub-skills, the plugin that ships this one along with the rest of its 16 skills, 1 command, 1 hook.

Wrote 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.

agentmods badge for triggers-and-applygates

README.md
[![agentmods](https://agentmods.dev/badge/skills/confighub/confighub-skills/triggers-and-applygates/github.svg)](https://agentmods.dev/skills/confighub/confighub-skills/triggers-and-applygates)
Your own site
<a href="https://agentmods.dev/skills/confighub/confighub-skills/triggers-and-applygates"><img src="https://agentmods.dev/badge/skills/confighub/confighub-skills/triggers-and-applygates/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.

agentmods 80×15 button for triggers-and-applygates

Your own site · 80×15
<a href="https://agentmods.dev/skills/confighub/confighub-skills/triggers-and-applygates"><img src="https://agentmods.dev/badge/skills/confighub/confighub-skills/triggers-and-applygates.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,255 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.04255
Opus 5 $0.00034 $0.02128
Sonnet 5 $0.00014 $0.00851
Haiku 4.5 $0.00007 $0.00426

Measured 2d ago against content hash 4778cac8e351, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

triggers-and-applygates 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 2d 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.

skills/triggers-and-applygates/SKILL.md · 261 lines

How it starts

The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.

triggers-and-applygates

Execution mode: follow references/execution-modes.md. This Skill grants no automatic tool permission. After reading current policy and exact scope, standalone use submits one requested Trigger, Filter, attachment, or native approval command to the host permission system; an external overlay may stop it before Bash.

Make validation enforced, not advisory. Without Triggers, vet-* functions are suggestions; with Triggers, they either block the apply path (a ValidationError) or flag it without blocking (a ValidationWarning) — see Blocking vs warning.

When to use

  • Setting up a new Space (or retrofitting existing Spaces) and the user wants policy to be enforced.
  • User asks "how do I make sure bad config can't be deployed?", "wire up schema validation", "add a policy", "require approval before apply".
  • User is diagnosing a Unit that won't apply and the reason might be a ValidationError, or wants to see what non-blocking ValidationWarnings a Unit carries.
  • User wants a check to advise rather than block (a --warn Trigger producing ValidationWarnings), or to flip an existing check between blocking and advisory.
  • Migrating validation from ad-hoc cub function vet vet-* calls to automatic enforcement.

Do not load for

  • One-off validation runs (use cub-mutate or a direct cub function vet vet-schemas …).
  • Authoring YAML (use confighub-core).
  • Fixing the config itself — this skill diagnoses and sets up gates; fixing is cub-mutate.

Preflight gates

  1. cub auth status succeeds — it contacts the server's /me endpoint to confirm the token is still valid (not just local login state). If it fails, ask the user to run cub auth login (an interactive browser sign-in an agent cannot complete).
  2. User has write permission on the platform Space (or whichever Space will hold Triggers) and on the target application Spaces.
  3. Confirm with the user: should Triggers be centralized in a platform Space, or do they already have a different convention? Default recommendation is platform.

Read the full file on GitHub · 261 lines

Files

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.

Changes

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.

  1. 2d ago Changed · -1 tokens per session 4778cac8e351
  2. 12d ago First seen · 261 lines · 69 tokens per session scan A 8f5f82538f8f

Subscribe to this mod's changes

triggers-and-applygates is a skill published in the GitHub repository confighub/confighub-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 4,255 once invoked, about $0.0003 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-31.

DevOps and cloud
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens