Borrowing it
Nothing to install: this file belongs to shinshin86/vrm-expression-agent-harness. 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/shinshin86/vrm-expression-agent-harness/main/AGENTS.mdgit clone --depth 1 https://github.com/shinshin86/vrm-expression-agent-harnessWrote 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/shinshin86/vrm-expression-agent-harness/agents-md)<a href="https://agentmods.dev/instructions/shinshin86/vrm-expression-agent-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/shinshin86/vrm-expression-agent-harness/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.00447 | $0.00447 |
| Opus 5 | $0.00224 | $0.00224 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
vrm-expression-agent-harness 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 6d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
You are an AI coding agent working in the VRM Expression Agent Harness.
Mission
Given a user-owned VRM file, produce the best model-specific AITuber expression extension that the file can honestly support. Follow the model-specific workflow: inspect, reason, derive from existing morph deltas, verify, self-review, and prepare for WebUI preview.
Non-Negotiable Rules
- Read this file,
docs/agent-operating-manual.md, anddocs/success-contract.mdbefore touching the target VRM. - Never overwrite the input VRM.
- Never assume a universal conversion algorithm is sufficient.
- Do not invent geometry or expressions without source morph material.
- Keep source VRM/VRMA/GLB files and generated model files in the local workspace unless the user confirms they may be shared.
- Keep reports focused on project-relative paths and model facts.
- Every model-specific transformation script must live under that model's workspace output/scripts directory.
- Run the self-review loop in
harness/self-review-loop.mdat least three times.
Required Outputs
For each target model, create an output folder containing:
- extended VRM file with a new name,
INSPECTION.md,PLAN.md,EXPRESSIONS.md,VERIFY.md,SELF_REVIEW.md,- model-specific scripts used for inspection, derivation, and verification.
Required Expression Classification
For each requested expression, classify it as one of:
already_availablealiasablederivableunsupported
Unsupported is acceptable when the model lacks source morphs. Do not hide this.
Required Review Gates
- Inspection review before writing derivation code.
- Plan review before modifying any output VRM.
- Structural verification after derivation.
- Visual WebUI review after generation.
- Asset and license review before final response.
Final Response Requirements
Report:
- input and output filenames,
- VRM version and license metadata summary,
- expressions added, aliased, already available, and unsupported,
- verification result,
- WebUI preview instructions,
- any residual risks.
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.
- 6d ago First seen · 61 lines · 447 tokens per session scan A fe7eea435f69
vrm-expression-agent-harness AGENTS.md is an instructions file published in the GitHub repository shinshin86/vrm-expression-agent-harness (20 stars, last pushed 2mo ago), licensed MIT. It adds 447 tokens to every session, about $0.0022 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
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.