Borrowing it
Nothing to install: this file belongs to huaweicloud/huaweicloud-devkit. 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/huaweicloud/huaweicloud-devkit/main/AGENTS.mdgit clone --depth 1 https://github.com/huaweicloud/huaweicloud-devkitWrote 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/huaweicloud/huaweicloud-devkit/agents-md)<a href="https://agentmods.dev/instructions/huaweicloud/huaweicloud-devkit/agents-md"><img src="https://agentmods.dev/badge/instructions/huaweicloud/huaweicloud-devkit/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.02174 | $0.02174 |
| Opus 5 | $0.01087 | $0.01087 |
| Sonnet 5 | $0.00435 | $0.00435 |
| Haiku 4.5 | $0.00217 | $0.00217 |
Grade A, and why
huaweicloud-devkit 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 7d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — HuaweiCloud Devkit
Commands
npm test # all tests (node --test)
npm run lint # ESLint + markdownlint
npm run lint:js # ESLint only
npm run lint:md # markdownlint only
npm run format # Prettier format all files
npm run format:check # Prettier check (no write)
npm run validate # structural validation
node --test test/structure.test.mjs # single test file
node ./scripts/validate-package.mjs # validation alone
No build step, no typecheck. One runtime dependency (undici for proxy support).
Architecture
This is an agent guidance + safety package, not a service encyclopedia. Six compact meta-skills route agent intent to the right capability path (Skills / KooCLI / API / SDK / MCP / Terraform).
plugins/huaweicloud-core/
skills/ ← 6 meta-skills + service skills
src/ ← Node.js MCP server (stdio JSON-RPC, 13 tools)
safety/ ← shared policy.json
hooks/ ← Python PreToolUse hook
.codex-plugin/ ← Codex plugin manifest
.claude-plugin/ ← Claude Code plugin manifest
.cursor-plugin/ ← Cursor plugin manifest
.officeace-plugin/← OfficeAce plugin manifest
.mcp.json ← MCP server config for agents
Safety is 3-layer: skills teach → hooks block → MCP/CLI wrappers enforce.
Skill Naming: Meta vs Service
- Meta-skills (
huaweicloud-*, 6 required): horizontal capability skills such as routing, discovery, CLI/auth, API/SDK, safety, troubleshooting. Agent always starts here. - Service skills (
huawei-*): vertical domain knowledge for specific Huawei Cloud services (ecs, obs, vpc, iam, dew, etc.). Loaded viahuaweicloud_retrieve_skillafter routing by the core meta-skill.
Required meta-skills (tethered to test/structure.test.mjs):
huaweicloud-api-and-sdk, huaweicloud-capability-discovery, huaweicloud-cli-and-auth, huaweicloud-core, huaweicloud-safety, huaweicloud-troubleshooting
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.
- 7d ago First seen · 141 lines · 2,174 tokens per session scan A b8ef8d2d1170
huaweicloud-devkit AGENTS.md is an instructions file published in the GitHub repository huaweicloud/huaweicloud-devkit (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,174 tokens to every session, about $0.0109 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
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).
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.
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).
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.