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/it235/multica-best-practices/agents-mdgit clone --depth 1 https://github.com/it235/multica-best-practicesWrote 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/it235/multica-best-practices/agents-md)<a href="https://agentmods.dev/instructions/it235/multica-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/it235/multica-best-practices/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 | $0.01379 | $0.01379 |
| Opus 5 | $0.00690 | $0.00690 |
| Sonnet 5 | $0.00276 | $0.00276 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
multica-best-practices 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 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is a practical Copy. Paste. Run. library of Agent · Squad · Skill · Issue templates for Multica. Every template can be copied and used as-is. Chinese is the source language of the content; this file is the agent entry point and is intentionally always in English (see the i18n convention below).
Project structure
README.md Project entry: quick start / principles / structure (bilingual switcher)
AGENTS.md Agent entry: project conventions and change rules (always English)
templates/ Everything copy-paste-ready (split by language)
├── zh_CN/ Chinese templates (default)
│ ├── agents/ Shared Agent Instructions (9 role definitions)
│ ├── skills/ Shared Skills (unified multica- prefix; see three-layer model)
│ │ ├── multica-gate-setup/ CI hard-gate templates ship inside this Skill
│ │ ├── multica-artifact-*-sync/ Orchestration skills landing content to team platforms (5; platform decoupled from roles)
│ │ └── multica-platform-*/ Platform-layer shells (Confluence/JIRA/Jenkins) — only place holding company-specific URLs/credentials
│ └── squad/ Squad starters (copy the whole subdirectory and run)
│ ├── software-development/ Regular development (recommended)
│ └── bug-fix/ Minimal fix combination
└── en_US/ English templates (same structure as zh_CN/)
docs/ Methodology (split by language: zh_CN/ + en_US/)
SECURITY.md Security check before sharing templates
Core conventions
- Skill naming:
multica-prefix + lowercase hyphenated; thenamefield inSKILL.mdmatches the directory name. - Skills mount by name: documents reference
multica-xxx(in backticks), never a repo path. - Agent naming:
role + project + member-id(e.g.BackendDev-user-service-u1024). - Directory semantics: inside each language tree,
agents/= roles,skills/= practices,squad/= squad combinations, anddocs/= methodology. CI hard-gate templates live in themultica-gate-setupskill; artifact landing to team platforms lives in the fivemultica-artifact-*-syncskills (seeartifact-conventions.md— platforms are decoupled from role prompts, swappable per company); there is no standalonegates/directory. - Three-layer skill model: content lives in role prompts (no platform names), orchestration lives in
multica-artifact-*-syncskills (which call a platform skill), and company-specific URLs/credentials live only inmultica-platform-*shells. Public repo ships content + orchestration + platform shells; a team fills the shells'config.yaml/scripts/without touching roles.
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 · 66 lines · 1,379 tokens per session scan A 43bb3509a0a7
multica-best-practices AGENTS.md is an instructions file published in the GitHub repository it235/multica-best-practices (89 stars, last pushed 10d ago), licensed MIT. It adds 1,379 tokens to every session, about $0.0069 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.