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/kaichen/amap-skill/agents-mdgit clone --depth 1 https://github.com/kaichen/amap-skillWhat 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.00588 | $0.00588 |
| Opus 5 | $0.00294 | $0.00294 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
amap-skill 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
- Core implementation lives in
skills/amap. - CLI entrypoint:
skills/amap/scripts/amap.ts. - Business logic modules:
skills/amap/scripts/lib/(validators.ts,commands.ts,endpoints.ts,http.ts,config.ts). - Tests live in
skills/amap/testswith JSON fixtures inskills/amap/tests/fixtures. - Reference docs and usage maps live in
skills/amap/references. - Root project config is in
package.json,tsconfig.json, andbun.lock.
Build, Test, and Development Commands
bun install: install dependencies frombun.lock.bun run test: run the repository test suite (cli.test.tsandcommands.test.ts).bun run amap:help: show CLI command help and supported flags.bun skills/amap/scripts/amap.ts geocode --address "<address>" [--city "<city>"]: run the CLI directly for local verification.- No separate build step is required; TypeScript is configured with
noEmit.
Coding Style & Naming Conventions
- Language: strict TypeScript (
tsconfig.jsonuses"strict": true). - Use 2-space indentation and explicit, readable function names.
- Keep command names and CLI flags in kebab-case (for example,
bike-route-address,origin-city). - Keep policy/validation centralized:
- Flag validation and defaults in
validators.ts. - Endpoint mapping and success criteria in
endpoints.ts. - Exit behavior in
config.ts(CliError,ExitCode).
- Flag validation and defaults in
- Prefer fail-fast checks for invalid inputs before making network calls.
Testing Guidelines
- Framework:
bun:test. - Test files use
*.test.tsnaming underskills/amap/tests. - Add fixture-based tests for API payload variants in
skills/amap/tests/fixtures. - For new commands, cover:
- Valid happy path.
- Invalid/unknown flag handling.
- AMap business-error responses.
- Network/error propagation (
ExitCode.NETWORK).
Commit & Pull Request Guidelines
- This checkout does not include local Git history; follow Conventional Commits by default (
feat:,fix:,refactor:,docs:). - Keep PRs focused and include:
- Why: problem and user impact.
- How: key implementation choices.
- Tests: exact commands executed and results.
- Link related issues and include CLI command examples when behavior changes.
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 · 50 lines · 588 tokens per session scan A 07c1865d9bf4
amap-skill AGENTS.md is an instructions file published in the GitHub repository kaichen/amap-skill (120 stars, last pushed 6mo ago), licensed MIT. It adds 588 tokens to every session, about $0.0029 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.
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).
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.