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/wix/skills/agents-mdgit clone --depth 1 https://github.com/wix/skillsWhat 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.00429 | $0.00429 |
| Opus 5 | $0.00215 | $0.00215 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
skills 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 3d 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
AGENTS.md
Read and follow CONTRIBUTING.md before editing this repository. It is the entry point;
docs/eval-scenarios.md holds the scenario format and docs/skill-evaluation.md explains the
automated checks. What they cover, one line each:
- Skill placement — no new top-level skills (admin-only); new content goes into an existing skill (
wix-manage,wix-app,wix-design-system,wix-headless), usually as a new reference. - Adding a wix-manage skill — a change is FOUR files, not one: the reference
.md+ theSKILL.mdindex entry + ayaml/wix-manage/<area>/documentation.yamlentry + an eval scenario underyaml/wix-manage-evals/<area>/. - wix-manage eval scenarios — every skill
.mdchange needs a covering scenario (the PR gate fails without one): aReadFullDocsArticletool-call assertion on<docsEntry>/skills/<slugified-title>plus anllm_judge. - Updating wix-app content — same rule, different mechanics: change +
SKILL.mdindex + a covering scenario underyaml/wix-app-evals/(skill_was_called+llm_judge), selected by tags derived from reference filenames — including negative dependencies. - Writing API skills — verify every API detail against official docs via the Wix MCP (or distill from a successful agent run); public APIs only, no internal service names; mutating flows ask the user first.
- Skill evaluation — PRs touching wix-manage references or yaml run the automated eval gate: coverage → schema → execution; treat it as a loop, not a one-time check.
- PR checklist — the pre-open checklist; walk it before every PR.
No fork PRs for wix-manage changes (the eval bot can't run on forks). Descriptions ≤ 1024 chars.
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.
- 3d ago First seen · 16 lines · 429 tokens per session scan A acdf16586c4d
skills AGENTS.md is an instructions file published in the GitHub repository wix/skills (28 stars, last pushed today), licensed MIT. It adds 429 tokens to every session, about $0.0021 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.