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 agentmods add instructions/charliechenye/skillgate/agents-mdgit clone --depth 1 https://github.com/charliechenye/SkillGateWrote 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/instructions/charliechenye/skillgate/agents-md)<a href="https://agentmods.dev/instructions/charliechenye/skillgate/agents-md"><img src="https://agentmods.dev/badge/instructions/charliechenye/skillgate/agents-md.svg" alt="Measured on agentmods" 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 | $0.00477 | $0.00477 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
SkillGate AGENTS.md 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SkillGate Agent Guide
This repository contains SkillGate, a deterministic static trust gate for AI-agent skills, instruction files, helper scripts, MCP metadata, MCP registry metadata, and MCP bundles.
Mission
Keep SkillGate focused on one review question:
What new agent capability would this artifact introduce?
The scanner should help reviewers make pre-install, pre-merge, and CI decisions without executing the artifact being reviewed.
Hard Invariants
- Do not execute scanned repository code, helper scripts, package commands, or MCP servers as part of scanning.
- Do not call LLM APIs, add telemetry, or upload findings automatically.
- Keep detection deterministic, static, and reproducible.
- Redact secret values; report secret names such as
GITHUB_TOKEN. - Prefer conservative extraction. If a host, command, or path is uncertain, leave it unknown instead of inventing a value.
- Preserve stable CLI, JSON, SARIF, policy schema, and rule semantics unless the task explicitly asks for a breaking change.
Implementation Guidance
- Read
README.md,future_steps.md, and the nearest tests before changing behavior. - Keep changes narrowly scoped to the requested behavior.
- Use existing rule, model, reporting, and fixture patterns instead of adding a new abstraction first.
- Add or update benchmark fixtures for scanner behavior changes.
- Update rule documentation when rule behavior changes so
skillgate rules listandskillgate explainstay complete. - Keep docs clear that SkillGate reports review signals and capability surfaces; it does not prove an artifact is safe.
Verification
Use the repository-local environment:
uv sync --locked --group dev
uv run pytest
uv run python tools/update_snapshots.py --check
uv run ruff check .
uv run ruff format --check .
npm test
For focused adoption docs and workflow checks:
uv run pytest tests/test_adoption_workflow.py
If uv cache access is unavailable in a restricted environment, use the checked
out virtual environment when present:
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.
- 4d ago First seen · 68 lines · 477 tokens per session scan A b9d23dfe2298
SkillGate AGENTS.md is an instructions file published in the GitHub repository charliechenye/SkillGate (2 stars, last pushed 16d ago), licensed MIT. It adds 477 tokens to every session, about $0.0024 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.
Other instructions, from other repositories
node9-proxy CLAUDE.md
Claude Code instructions for node9-ai/node9-proxy, covering node9 proxy — claude code rules, pr checklist (required before every commit), test rules, code rules and architecture notes.
Doberman-Core AGENTS.md
AGENTS.md instructions for DobermanCore/Doberman-Core, covering claude.md — doberman operating manual, 0. on startup (every session), 1. what this repository is, 2. architecture & extension points and 3. prime directives (non-negotiable).
trustabl CLAUDE.md
Claude Code instructions for trustabl/trustabl, covering instructions for claude — trustabl, project naming, detection model: five scopes, scanning pipeline and step 1 — recon (cheap, no ast).
trustabl GEMINI.md
Gemini CLI instructions for trustabl/trustabl, a project described as: Fix agent reliability issues across Claude, OpenAI, Google ADK, MCP, LangChain, CrewAI, AutoGen, Pydantic AI, and Vercel AI.
saferskills CLAUDE.md
Claude Code instructions for OpenLatch/saferskills, covering claude.md — saferskills, quick start, backend, frontend and codegen.
diplomat-agent AGENTS.md
Instructions for Diplomat-ai/diplomat-agent, covering agents.md — for ai coding assistants (v0.3.0), what this repo is, architecture, key design decisions and running tests.