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/archcore-ai/cli/agents-mdgit clone --depth 1 https://github.com/archcore-ai/cliWhat 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.02684 | $0.02684 |
| Opus 5 | $0.01342 | $0.01342 |
| Sonnet 5 | $0.00537 | $0.00537 |
| Haiku 4.5 | $0.00268 | $0.00268 |
Grade A, and why
cli 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Agent Instructions
Purpose
This repository develops the Archcore CLI, MCP server, host integrations, and document templates.
Write technical documentation so that human readers and AI agents can identify the subject, understand the constraints, and apply the information without guessing.
Two profiles govern every document: an ASD-STE100-inspired profile constrains the sentence, and an ISO 24495-1-inspired profile constrains the structure. Both apply everywhere; the document type decides which half binds and which half advises.
The assignment — profile, line format, and metric per document type — lives in the shared Archcore rule concepts/document-prose-canon, mounted read-only from the archcore global source. Do not restate that assignment here, and do not classify a document into a profile by hand when the rule already assigns one to its type.
This policy is an internal writing profile. It is not a claim of compliance, certification, or approval by ASD, ISO, or any standards organization.
Scope
Apply this policy when creating or updating:
.archcore/**/*.md;README.md;docs/**/*.md;templates/**/*.md;- Markdown embedded in Go source;
- CLI help text and error messages;
- MCP tool descriptions and prompts;
- agent instruction files;
- user-facing installation, migration, recovery, and troubleshooting instructions.
Do not rewrite or translate:
- Go identifiers;
- package names;
- commands;
- flags;
- paths;
- configuration keys;
- MCP tool names;
- JSON fields;
- document type names;
- literal values;
- generated output;
- exact quotations from external sources.
Precedence
Apply instructions in this order:
- Explicit user requirements.
- Accepted rules and decisions in
.archcore/. - Type-specific document contracts and templates.
- This repository writing policy.
- General stylistic preferences.
When instructions conflict, follow the higher-priority instruction.
Archcore-first context
Before researching project behavior, architecture, conventions, or implementation approaches:
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 · 306 lines · 2,684 tokens per session scan A e563a15642fa
cli AGENTS.md is an instructions file published in the GitHub repository archcore-ai/cli (61 stars, last pushed 15d ago), licensed Apache-2.0. It adds 2,684 tokens to every session, about $0.0134 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
cocoindex AGENTS.md
AGENTS.md instructions for cocoindex-io/cocoindex, covering agents.md, build and test commands, building, testing and code formatting and linting.
apm python.instructions.md
Python development guidelines.
framework AGENTS.md
Instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
packmind packmind-rest-api-endpoint-design.instructions.md
Instructions for PackmindHub/packmind: Conventions for designing REST API endpoints that are predictable, self-documenting, and aligned with distinct business actions. Favors dedicated action endpoints over generic status updates, and rout... .
Commit Message
Comprehensive Conventional Commits guidelines for openwebui-extensions.
SwarmAI CLAUDE.md
Instructions for xg-gh-25/SwarmAI, covering claude.md, before you push — the local quality gate, commit identity, dev commands and conventions & invariants.