agentmods.dev

bedside: Instructions file for Codex

AGENTS.md

bedside AGENTS.md is an instructions file for Codex, OpenCode from tig/bedside. It costs 601 tokens per session, scanned A, original, Apache-2.0.

A set of repository instructions for coding agents working on the tig/bedside project. It explains the project structure, writing rules, command-line architecture, and how agents should ask the operator for approval.

In plain words
What is it for?
Guiding edits and other agent work in the Bedside repository, including documentation style, image handling, project paths, and approval steps.
Why use it?
It gives agents project-specific rules and keeps sensitive or high-judgment actions behind explicit human decisions. It also points them to the correct files and workflows.

Instructions file for CodexOpenCode

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

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

not rated 4repo 3mo ago A scan 601 tokens original Apache-2.0
View source ↗ tig/bedside
Reuse

Borrowing it

Nothing to install: this file belongs to tig/bedside. 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/tig/bedside/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/tig/bedside

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 bedside AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tig/bedside/agents-md"><img src="https://agentmods.dev/badge/instructions/tig/bedside/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 601 This file is loaded in full into every session.
When invoked 601 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.00601 $0.00601
Opus 5.5 $0.00240 $0.00240
Sonnet 5.5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured 2mo ago against content hash 62c3d0368c77, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bedside 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 2mo 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 · 57 lines

How it starts

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

AGENTS.md

Project guidance for AI coding agents working in tig/bedside.

What this repo is

Portable Bedside standard: contract/, surface/, eval/, plus a minimal Python CLI (src/bedside/). Not silico. Not mcec. Not domain product UX.

Human index: README.md. Writing style: follow Tig voice mechanics (no em-dashes, no horizontal rules, short paragraphs, Oxford commas, sentence-ended list items) when editing prose.

Brand images: docs/images/README.md. Canonical docs/images/hero.jpg (README) and docs/images/social-preview.jpg (GitHub 1280×640). Export social with python scripts/export_social_preview.py.

Help the operator (Bedside)

We follow Bedside: manners for agents operating tools for smart, high-judgment non-experts.

  • Pin: see bedside.toml (do not soft-fork tenets).
  • Normative contract path: contract
  • Human gates: call bedside ask / bedside step (or the host structured choice UI).

Summary (full contract is normative):

  1. Assume low ops literacy, high judgment.
  2. No walls of shell or choice.
  3. Prefer doing over instructing.
  4. No silent work.
  5. Human acts are explicit and dumb-simple.
  6. Own first-time setup from zero.
  7. Own scary surfaces in plain language.
  8. Confirm what they can see, in their words.
  9. Never leave them at a cliff.
  10. Teach only what tomorrow requires.
  11. Compound what you learn.

Domain notes (this repo only)

  • First-run: pip install -e ".[dev]" then bedside doctor and bedside eval.
  • Scary surfaces: none physical; prefer doing install and tests yourself.
  • Leave-behind: pytest -q and bedside eval (one proof path for manners).

CLI architecture

  • bedside.cli: argparse adapter only.
  • bedside.commands.*: UI-agnostic command cores (future tui-cs/cli should call these).
  • bedside.eval_engine: rule-based R1-R11 scoring.
  • Operator gates: ask (structured choice) and step (one human act + confirm).
  • Exit codes: 0 ok, 10 human-needed / non-recommended ask / declined step, 20 manners fail, 30 setup error.

Read the full file on GitHub · 57 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. 2mo ago First seen · 57 lines · 601 tokens per session scan A 62c3d0368c77

Subscribe to this mod's changes

bedside AGENTS.md is an instructions file published in the GitHub repository tig/bedside (4 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 601 tokens to every session, about $0.0024 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.

agent-orchestrationagent-skillsagentic-aiagentic-workflowaibedside
Related

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

microsoft/vscode · 9,715 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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens