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/aidotnet/moyucode/agents-mdgit clone --depth 1 https://github.com/AIDotNet/MoYuCodeWhat 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.01224 | $0.01224 |
| Opus 5 | $0.00612 | $0.00612 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
MoYuCode 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 2d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/MoYuCode/: ASP.NET Core Web API (net10.0) with EF Core (SQLite).Api/: minimal API endpoint mappings (seeApiEndpoints.cs).Controllers/: REST controllers.Data/:MyYuCodeDbContextand entity models.Contracts/andServices/: shared DTOs and business logic.
web/: Vite + React + TypeScript UI.web/src/: app code; the@/alias maps here.web/public/: static assets; build output inweb/dist/.
MoYuCode.slnx: solution referencing the backend project.
Build, Test, and Development Commands
Backend:
dotnet build src/MoYuCode/MoYuCode.csproj— compile the API.dotnet run --project src/MoYuCode/MoYuCode.csproj --launch-profile http— run onhttp://localhost:9110(use--launch-profile httpsforhttps://localhost:9111).
Frontend (from web/):
npm ci— install dependencies (usespackage-lock.json).npm run dev— start Vite dev server.npm run build— typecheck and build toweb/dist/.npm run lint— run ESLint.
Coding Style & Naming Conventions
- C#: 4-space indentation; nullable reference types are enabled—avoid introducing new warnings. Use
PascalCasefor types/methods andcamelCasefor locals/parameters. - Frontend: components in
PascalCase.tsx, hooks inuseX.ts. Prefer importing via@/…when applicable. - Formatting: no repo-wide formatter is enforced; keep diffs focused and run lint before opening a PR.
Testing Guidelines
- Automated tests are not set up yet (no
*.Tests.csprojor JS test runner). If adding tests, place them undertests/and ensuredotnet testruns.
Commit & Pull Request Guidelines
- Git history is empty; use a consistent convention going forward (e.g., Conventional Commits:
feat: …,fix: …,chore: …). - PRs should include a short summary, testing notes (commands run), and screenshots for UI changes. Avoid committing build artifacts (
bin/,obj/,web/dist/,web/node_modules/).
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.
- 2d ago First seen · 87 lines · 1,224 tokens per session scan A 2ed712a22b40
MoYuCode AGENTS.md is an instructions file published in the GitHub repository AIDotNet/MoYuCode (84 stars, last pushed 7mo ago), licensed MIT. It adds 1,224 tokens to every session, about $0.0061 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
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.
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).
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.