Borrowing it
Nothing to install: this file belongs to Arclude/Arterm-CLI. 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/Arclude/Arterm-CLI/main/AGENTS.mdgit clone --depth 1 https://github.com/Arclude/Arterm-CLIWrote 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/arclude/arterm-cli/agents-md)<a href="https://agentmods.dev/instructions/arclude/arterm-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/arclude/arterm-cli/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/arclude/arterm-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/arclude/arterm-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00641 | $0.00641 |
| Opus 5.5 | $0.00256 | $0.00256 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
Arterm-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 1mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Development Workflow
- Stay on your own branch - Do not take, cherry-pick, merge, or copy code from other
people's or other agents' branches unless the source branch belongs to a repository
maintainer and the user explicitly asks you to integrate it. Only work from your branch
and its base (e.g.
main) otherwise. Never integrate branches owned by non-maintainers or other agents yourself; tell the user and let them decide how to proceed.
Install Notes
~/.local/bin/artermis the launcher symlink used fromPATH.~/.arterm/builds/current/artermis the active local/source-build channel; self-dev builds andscripts/install_release.shpoint the launcher here.~/.arterm/builds/stable/artermis the stable release channel;scripts/install.shinstalls this and points the launcher here.~/.arterm/builds/versions/<version>/artermstores immutable binaries.~/.arterm/builds/canary/artermstill exists for canary/testing flows, but it is not the primary self-dev install path.- On Windows, the equivalents are
%LOCALAPPDATA%\\arterm\\bin\\arterm.exefor the launcher,%LOCALAPPDATA%\\arterm\\builds\\stable\\arterm.exefor stable, and%LOCALAPPDATA%\\arterm\\builds\\versions\\<version>\\arterm.exefor immutable installs;scripts/install.ps1currently installs the stable channel. - Ensure
~/.local/binis before~/.cargo/bininPATH.
Verifying a change at runtime
cargo build alone proves nothing about behavior. arterm run and interactive
sessions are served by the long-lived daemon at
~/.arterm/builds/shared-server/arterm, which is a symlink into
~/.arterm/builds/versions/<version>/. Until that symlink is repointed and the
daemon restarted (arterm self-dev --build), a freshly built binary is inert and
every runtime check silently measures the old code.
To test a change without disturbing the shared daemon or the caller's session, run your build against its own socket:
cargo build --profile selfdev
./target/selfdev/arterm run --no-update --socket /run/user/1000/arterm-mytest.sock '<prompt>'
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.
- 1mo ago First seen · 45 lines · 641 tokens per session scan A adb6811fe2e6
Arterm-CLI AGENTS.md is an instructions file published in the GitHub repository Arclude/Arterm-CLI (2 stars, last pushed 1mo ago), licensed MIT. It adds 641 tokens to every session, about $0.0026 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.