Borrowing it
Nothing to install: this file belongs to WingedGuardian/skyrimvr-claude-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WingedGuardian/skyrimvr-claude-toolkit/master/AGENTS.mdgit clone --depth 1 https://github.com/WingedGuardian/skyrimvr-claude-toolkitWrote 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/wingedguardian/skyrimvr-claude-toolkit/agents-md)<a href="https://agentmods.dev/instructions/wingedguardian/skyrimvr-claude-toolkit/agents-md"><img src="https://agentmods.dev/badge/instructions/wingedguardian/skyrimvr-claude-toolkit/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.1 | $0.00737 | $0.00737 |
| Opus 5 | $0.00368 | $0.00368 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
skyrimvr-claude-toolkit 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 8d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working in this Skyrim modding environment.
Read CLAUDE.md first — it is the full project instruction set, and it is agent-neutral apart
from the parts noted below. It contains the configured paths for this install, the tool inventory and
how to invoke each one, the ESP-editing workflows, and the core working principles. KNOWLEDGEBASE.md
is the reference for engine quirks and version differences; consult it before making changes rather
than after something breaks.
This file exists so agents that look for AGENTS.md by convention find their way in. It deliberately
does not duplicate CLAUDE.md, so the two cannot drift apart.
What is portable, and what is not
Portable to any agent — this is most of the toolkit by volume:
KNOWLEDGEBASE.md— engine behaviour, VR/SE/AE differences, tool gotchas. Plain reference.CLAUDE.md— paths, tool usage, workflows, principles.- Everything under
tools/,examples/, andscripts/— plain bash, Node, and Python. No agent runtime is involved; they work from any shell.
Claude Code specific — you do not get these:
.claude/settings.jsonand.claude/hooks/— the safety layer. These hooks are what block direct writes to ESP/ESM/BSA files, require confirmation before editing anything in the game or config directories, and auto-back-up every file before it is modified, with an audit trail..claude/skills/— packaged workflows.
Read that second list carefully. On another agent the guardrails are simply absent. Nothing will
stop a bad rm, a direct binary write into a plugin, or an unreviewed edit to a live INI. The
knowledge and the tools carry over; the seatbelts do not.
If you are not running under Claude Code, compensate deliberately:
- Back up before you touch anything. Copy the file first — the toolkit's own convention is
.claude/backups/<descriptive-name>/. Assume nothing is doing this for you. - Never write directly to
.esp/.esm/.esl/.bsa/.ba2. Use Spriggit (serialize to YAML, edit the YAML, deserialize) or xelib. A hand-edited plugin binary is a corrupted plugin. - Show the user the change before applying it, especially for INIs, load order files, and anything under the game directory. The hooks normally force this pause; without them it is on you.
- Snapshot
.pscsources before experimenting. They are not covered by any automatic backup even under Claude Code, and reconstructing a working script from memory is miserable.
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.
- 8d ago First seen · 54 lines · 737 tokens per session scan A 02a2283d9613
skyrimvr-claude-toolkit AGENTS.md is an instructions file published in the GitHub repository WingedGuardian/skyrimvr-claude-toolkit (13 stars, last pushed yesterday), licensed MIT. It adds 737 tokens to every session, about $0.0037 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.