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 arunveersingh/ai --skill day-11-premise-gategit clone --depth 1 https://github.com/arunveersingh/aiWrote 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/arunveersingh/ai/day-11-premise-gate)<a href="https://agentmods.dev/skills/arunveersingh/ai/day-11-premise-gate"><img src="https://agentmods.dev/badge/skills/arunveersingh/ai/day-11-premise-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/arunveersingh/ai/day-11-premise-gate"><img src="https://agentmods.dev/badge/skills/arunveersingh/ai/day-11-premise-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.00099 | $0.00661 |
| Opus 5.5 | $0.00040 | $0.00264 |
| Sonnet 5.5 | $0.00020 | $0.00132 |
| Haiku 4.5 | $0.00010 | $0.00066 |
Grade A, and why
premise-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 13d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Premise gate
A reconciliation plan flags "settlement file timestamps are UTC" with no source. You approve it; T2–T4 start on it over the afternoon. The file is Amsterdam local time, so payments made just after midnight land on the wrong day and false discrepancy tickets go out every night.
Flagged is not gated. No source, no start, and the answer lives in the plan.
Part A — Ask (paste after your ticket)
Plan the tasks before writing code. List premises as:
P<n> | claim | KNOWN or UNKNOWN | source I can open | how to resolve
Reasoning and defaults are UNKNOWN. Each task: T<n> | title | needs: P<n>, ...
Before starting any task, re-check its premises in the plan. If one is UNKNOWN, don't start it. Reply:
BLOCKED: premise P<n> unknown | found: T<n> needs "<claim>", no source | need: <what settles it>
Start tasks that need nothing unknown. When I resolve a premise, update its line with the source.
In an orchestrated flow (spec → plan → tasks → implement): the premise table lives in the plan file; each task lists needs; your project rules say "check premises before starting a task". Resolved sources go into the plan so the next session inherits them.
Part B — Gate (you do this)
gate.py has no dependencies. Put the plan in JSON (see plan.example.json) and run it before a task starts:
python3 gate.py plan.json # every task
python3 gate.py plan.json T3 # one task; exit 0 may start, 1 blocked or unknown id
On the example: T1: may start, then T2: BLOCKED: premise P1 unknown | found: T2 needs "settlement file timestamps are UTC", no source | need: payment provider's file spec, and the same for T3 and T4.
- Open every KNOWN source. If it doesn't say what the claim says, it's UNKNOWN.
- Resolve with a lookup or a decision, not a better guess. Write the source into the plan.
- A risky task with
needs: []deserves a question: what is it relying on?
Limit: the gate checks status, not truth. A wrong or stale source passes.
What ships with it
2 files 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.
- 13d ago First seen · 45 lines · 99 tokens per session scan A c80a091edcfb
premise-gate is a skill published in the GitHub repository arunveersingh/ai (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 99 tokens to every session and 661 once invoked, about $0.0004 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-10-13.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…