vibepod-cli: Instructions file for Codex

AGENTS.md

vibepod-cli AGENTS.md is an instructions file for Codex, OpenCode from VibePod/vibepod-cli. It costs 721 tokens per session, scanned A, original, MIT.

A project instruction file that stores lasting knowledge for coding agents, such as how to build, test, release, and change the project.

In plain words
What is it for?
Use it to guide project maintenance, add supported agents, configure local image fallbacks, and run the project's tests.
Why use it?
It keeps important project rules and discoveries with the code, so agents do not have to rediscover them. It also lists every place that must change when adding support for another agent.

Instructions file for CodexOpenCode

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

This is VibePod/vibepod-cli's own configuration. It tells Codex and OpenCode how to work on vibepod-cli 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 vibepod-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to VibePod/vibepod-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.

Copy the file
curl -O https://raw.githubusercontent.com/VibePod/vibepod-cli/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/VibePod/vibepod-cli

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 vibepod-cli AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/vibepod/vibepod-cli/agents-md/github.svg)](https://agentmods.dev/instructions/vibepod/vibepod-cli/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/vibepod/vibepod-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/vibepod/vibepod-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.

agentmods 80×15 button for vibepod-cli AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/vibepod/vibepod-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/vibepod/vibepod-cli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 721 This file is loaded in full into every session.
When invoked 721 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.00721 $0.00721
Opus 5.5 $0.00288 $0.00288
Sonnet 5.5 $0.00144 $0.00144
Haiku 4.5 $0.00072 $0.00072

Measured 19d ago against content hash 50fc2c4599d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibepod-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 19d 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 · 52 lines

How it starts

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

Project agent memory

This file is the project's committed home for project-intrinsic agent knowledge: build, test, release, architecture, and sharp-edge notes that should travel with the code.

  • Add durable project-specific notes here as they are discovered through real work.

Adding a supported agent

To add a new agent, mirror the qwen (or freebuff) entry end-to-end: SUPPORTED_AGENTS/AGENT_SHORTCUTS/AGENT_ALIASES/IMAGE_OVERRIDE_ENV_KEYS and get_default_images() in src/vibepod/constants.py, the AGENT_SPECS entry in src/vibepod/core/agents.py (mount contract must match the vibepod-agents image entrypoint; set acp_command when the agent ships an ACP adapter, see docs/acp.md), the per-agent defaults in src/vibepod/core/config.py, skills paths in src/vibepod/commands/run.py::_agent_skill_paths, and the docs + tests (docs/agents/index.md, README.md, docs/quickstart.md, docs/index.md, docs/configuration.md, tests/test_{agents,cli,constants,run,task_cmd}.py). The local-image fallback (VP_IMAGE_<AGENT> override + pull-failure fallback in run.py/task.py) is how an unreleased image is exercised locally.

Hermes is the exception to the ~/.agents/skills convention: it reads that directory only via the skills.external_dirs key in its own config.yaml and has no env-var override, so the vibepod-agents image entrypoint seeds the key rather than the CLI mounting a symlink.

Hermes also has two launch constraints enforced by validate_rootless_runtime and the ACP reserved-path check: it is rejected on rootless Podman (the pinned image needs its own runtime user and rejects the UID rootless keep-id maps the container to, including 0), and /opt/hermes (its install root) is reserved so an --acp workspace bind cannot shadow the entrypoint/venv/hermes-acp.

Mistral Vibe uses the canonical ID vibe (devstral is a CLI/config alias). Its published devstral image and credentials subdirectory are retained for compatibility; VP_IMAGE_VIBE takes precedence over VP_IMAGE_DEVSTRAL.

Read the full file on GitHub · 52 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. 19d ago Changed · +4 lines · +59 tokens per session 50fc2c4599d0
  2. 1mo ago Changed · +11 lines · +167 tokens per session ca12e0b54d51
  3. 1mo ago Changed · +1 lines · +23 tokens per session f835c125cd76
  4. 1mo ago First seen · 36 lines · 472 tokens per session scan A dfbb639dec5b

Subscribe to this mod's changes

vibepod-cli AGENTS.md is an instructions file published in the GitHub repository VibePod/vibepod-cli (187 stars, last pushed 15d ago), licensed MIT. It adds 721 tokens to every session, about $0.0029 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-30.

Related

Other instructions, from other repositories