agentmods.dev

arch-tuner: Instructions file for Codex

AGENTS.md

arch-tuner AGENTS.md is an instructions file for Codex, OpenCode from xrhstosmour/arch-tuner. It costs 2,480 tokens per session, scanned A, original, MIT.

Repository instructions for Arch Tuner, a toolkit that hardens Arch Linux virtual private servers by changing system settings and installing packages.

In plain words
What is it for?
Use them when modifying Arch Tuner's installation phases, security or privacy helpers, configuration files, shared shell functions, or tests.
Why use it?
They give coding agents the project context, required order of operations, runtime rules, and local testing guidance before they change the toolkit.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is xrhstosmour/arch-tuner's own configuration. It tells Codex and OpenCode how to work on arch-tuner itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything arch-tuner configures →

not rated 11repo 27d ago A scan 2,480 tokens original MIT
View source ↗ xrhstosmour/arch-tuner
Reuse

Borrowing it

Nothing to install: this file belongs to xrhstosmour/arch-tuner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/xrhstosmour/arch-tuner/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/xrhstosmour/arch-tuner

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for arch-tuner AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xrhstosmour/arch-tuner/agents-md.svg)](https://agentmods.dev/instructions/xrhstosmour/arch-tuner/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/xrhstosmour/arch-tuner/agents-md"><img src="https://agentmods.dev/badge/instructions/xrhstosmour/arch-tuner/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,480 This file is loaded in full into every session.
When invoked 2,480 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02480 $0.02480
Opus 5 $0.01240 $0.01240
Sonnet 5 $0.00496 $0.00496
Haiku 4.5 $0.00248 $0.00248

Measured 8d ago against content hash 64dbb188f21e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

arch-tuner 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 8d 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.

AGENTS.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent guide

Tips and rules for any AI agent working in this repository. Read this first.

What this repository is

Arch Tuner is an Arch Linux VPS hardening toolkit. install.sh drives three phases in order:

  • scripts/utilities/essentials.sh: package manager configuration, essential packages, shell setup.
  • scripts/utilities/privacy.sh: privacy-hardening helpers under scripts/helpers/privacy/.
  • scripts/utilities/security.sh: security-hardening helpers under scripts/helpers/security/.

documents/roadmap.md is the living plan, what phases exist, what the current pull request series adds, and what remains. Read it before picking up work.

Architecture

  • scripts/core/: constants.sh for static values, flags.sh for documented defaults. Both are sourced before the runtime state file, so runtime values can override them.
  • scripts/helpers/functions/: shared utilities every helper sources, see below.
  • scripts/helpers/essentials/, scripts/helpers/privacy/, scripts/helpers/security/: one file per feature, called from the matching scripts/utilities/*.sh.
  • scripts/configurations/<phase>/<feature>/: config payloads a helper copies onto the host. Bash payloads need #!/bin/bash. Fish payloads use the .fish extension.
  • scripts/packages/<phase>/<feature>.txt: plain text, one package per line.
  • systemd/: standalone unit files a helper deploys to /etc/systemd/system/, for units that don't fit the drop-in pattern.

Runtime state and local testing

  • Runtime state lives in /var/lib/arch-tuner/state.sh, written by change_flag_value in scripts/helpers/functions/state.sh and sourced by source_state after constants.sh and flags.sh, so it overrides their defaults. reset_state deletes it.
  • Set ARCH_TUNER_STATE_DIRECTORY to point the state file somewhere else for testing, so a local run never touches /var/lib/arch-tuner on your machine: ARCH_TUNER_STATE_DIRECTORY=/tmp/arch-tuner-test sh scripts/helpers/security/sysctl.sh.
  • Run a single helper directly with sh scripts/helpers/security/<name>.sh instead of the whole install.sh flow, most helpers only need their own config and package list to do anything useful. install.sh itself reboots between the essentials and privacy phases, so it is not meant to be re-run repeatedly while iterating on one helper.
  • Every helper is idempotent through compare_files or are_packages_installed, safe to run more than once, a second run should report no changes and skip service restarts.

Read the full file on GitHub · 169 lines

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.

  1. 8d ago First seen · 169 lines · 2,480 tokens per session scan A 64dbb188f21e

Subscribe to this mod's changes

arch-tuner AGENTS.md is an instructions file published in the GitHub repository xrhstosmour/arch-tuner (11 stars, last pushed 27d ago), licensed MIT. It adds 2,480 tokens to every session, about $0.0124 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.

arch-linuxprivacyservertoolstuning
Related

Other instructions, from other repositories

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens