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 wiolett-industries/marketplace --skill intent-gategit clone --depth 1 https://github.com/wiolett-industries/marketplaceWrote 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/wiolett-industries/marketplace/intent-gate)<a href="https://agentmods.dev/skills/wiolett-industries/marketplace/intent-gate"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/intent-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/wiolett-industries/marketplace/intent-gate"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/intent-gate.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.00061 | $0.00540 |
| Opus 5 | $0.00030 | $0.00270 |
| Sonnet 5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
intent-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 11d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Gate
Determine what the user actually wants, whether the obvious reading is safe, and which primary path and assurance profile fit. This is a brief local routing decision, not optional ceremony and not an automatic subagent step.
Gate
- State the intended outcome internally in one sentence.
- Identify only misreads that could materially change scope, safety, or user-visible behavior.
- Inspect cheap repository facts that can resolve them.
- Choose complexity (
simple,medium,complex,very_complex) for execution shape and assurance (fast,standard,assurance, explicit audit) for risk. - Set a change envelope: requested behavior, expected change class, expected surfaces, must-preserve constraints, and explicit non-goals.
- Choose the next module or direct path.
- Ask only when remaining ambiguity is material and a reasonable assumption would be costly, irreversible, or behavior-changing.
Use L0 for content/config-only changes, L1 for a localized behavior change, L2 for a cross-module contract or reusable abstraction, and L3 for a new subsystem/platform layer. Do not silently raise the class. A new API/schema/protocol/shared abstraction/layer outside the expected envelope requires a narrower alternative, explicit justification, or a material user question.
Before presenting any material plan, architecture decision, or scope-expanding solution, take one local second look from existing context: compare it with the request and envelope, remove unsupported scope, and choose KEEP, SHRINK, ASK, or REPLAN. Do this silently for chat-only work; do not add an agent or discovery pass.
When confidence is high, continue without printing a gate report. When a decision must be exposed, report only intent, assumption/question, assurance, and next path.
Independent Intent Review
Use read-only workflow_intent_reviewer only when all are true:
- assurance risk applies;
- material ambiguity remains after cheap inspection;
- independent interpretation could prevent a high-impact misread;
- the task-wide agent budget permits it.
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.
- 11d ago First seen · 38 lines · 61 tokens per session scan A 1ee6f6317169
intent-gate is a skill published in the GitHub repository wiolett-industries/marketplace (10 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 540 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-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…