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/arclude/arterm-cli/agents-mdgit clone --depth 1 https://github.com/Arclude/Arterm-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.00641 | $0.00641 |
| Opus 5 | $0.00320 | $0.00320 |
| Sonnet 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 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 — 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.
- yesterday 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 yesterday), licensed MIT. It adds 641 tokens to every session, about $0.0032 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
Lim-Code AGENTS.md
Instructions for Lianues/Lim-Code, covering agents.md, skill 编写兜底入口 and subagents 使用兜底入口.
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
com-example-config-AsyncTestConfig
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.