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/arenadata/adcm-agent/agents-mdgit clone --depth 1 https://github.com/arenadata/adcm-agentWhat 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.01902 | $0.01902 |
| Opus 5 | $0.00951 | $0.00951 |
| Sonnet 5 | $0.00380 | $0.00380 |
| Haiku 4.5 | $0.00190 | $0.00190 |
Grade A, and why
adcm-agent 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 yesterday.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring contract
How skills, commands, agents and scripts in this repository are written. Read this before
adding or editing one. tools/validate_skills.py and tools/check_scripts.py enforce the
mechanical half; the rest is style you are expected to match by hand.
Repository layout
.claude-plugin/
plugin.json # every skill directory must be listed in skills[]
marketplace.json # one plugin entry, source "./"
skills/<skill-name>/
SKILL.md # required
reference/*.md # optional: lookup material (tables, inventories, key lists)
commands/*.md # slash commands
agents/*.md # subagents
scripts/ # what the skills actually run - shipped to users
tools/ # this repository's own validation - not shipped as behaviour
Skill directories are kebab-case and always prefixed adcm-. SKILL.md is always
uppercase. Commands are prefixed adcm- too, so they read as /adcm-build.
The rule this repository exists to enforce
No file here may contain a real ADCM instance address, account, credential or host name. Not in a skill, not in a command, not in a script default, not in a docstring, not in an example.
This is not a style preference. The skills this plugin replaces defaulted to one
development stand's IP address and to admin/admin, which made them wrong for every other
installation and put a credential in three git repositories. Everything instance-specific
resolves at run time through scripts/adcm_env.py.
Both validators check this, and they check prose as well as code:
- a literal IPv4 address that is not loopback or an RFC 5737 documentation range
- an
os.environ.get("ADCM_*", "<fallback>")with a baked-in default - a default account pair used as a value
- a credential-looking assignment whose value is not a placeholder or an env var name
Write <ask the user>, $ADCM_URL, MY_VAR, adcm.example.internal instead.
Frontmatter
---
name: adcm-<topic> # must equal the directory name
description: <what it does> - <inventory of the concepts it covers>. Use when <trigger>, <trigger>, or <symptom>.
license: Apache-2.0
metadata:
author: Arenadata
version: "0.1.0"
adcmVersion: "2.x (API v2)"
---
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.
- yesterday First seen · 160 lines · 1,902 tokens per session scan A 57d03c388874
adcm-agent AGENTS.md is an instructions file published in the GitHub repository arenadata/adcm-agent (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 1,902 tokens to every session, about $0.0095 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-31.
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.