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/wwbweibo/live2d-assistant/copilot-instructionsgit clone --depth 1 https://github.com/wwbweibo/live2d-assistantWrote 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/wwbweibo/live2d-assistant/copilot-instructions)<a href="https://agentmods.dev/instructions/wwbweibo/live2d-assistant/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/wwbweibo/live2d-assistant/copilot-instructions.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.01365 | $0.01365 |
| Opus 5 | $0.00682 | $0.00682 |
| Sonnet 5 | $0.00273 | $0.00273 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
live2d-assistant copilot-instructions.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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions — Live2D Assistant
Project Overview
Multi-platform (Web/Electron) assistant with Live2D avatar + AI chat, powered by a multi-agent system.
live2d-assistant-fe/ → Vue 3 + Vite + TypeScript (UI)
live2d-assistant-server/ → Python FastAPI (API + Agent orchestration)
external/agentic-agent/ → git submodule: agentic-agents framework
electron-live2d/ → Electron desktop shell
Build & Run
Frontend
cd live2d-assistant-fe
npm install && npm run dev # dev → localhost:5173
npm run build # prod → dist/
Backend
cd live2d-assistant-server
uv sync
uv run fastapi run main.py --host 0.0.0.0 --port 8000
# Add --static_path ../live2d-assistant-fe/dist to serve frontend
Electron
cd electron-live2d && npm install && npm run start
Architecture
Communication
- REST API + SSE streaming (
POST /api/agentic/chat) - CORS: allow all origins
SSE Event Format (from AgentSession.process_message())
Events use resp_type field:
resp_type |
Payload fields | Description |
|---|---|---|
status |
content |
Agent thinking status |
text |
agent, content |
Streamed text output |
tool_result |
agent, content |
Tool execution result |
transfer |
from_agent, to_agent, reason |
Agent handoff |
error |
content |
Error message |
finished |
content |
Task complete |
Agent System
Framework: agentic-agents (submodule at external/agentic-agent)
Flow: User → AgentSession → Router Agent → transfer_to_<Name>() → Specialist Agent → transfer_to_Router() → done
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 · 123 lines · 1,365 tokens per session scan A af73af272817
live2d-assistant copilot-instructions.md is an instructions file published in the GitHub repository wwbweibo/live2d-assistant (11 stars, last pushed 5mo ago), licensed MIT. It adds 1,365 tokens to every session, about $0.0068 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.