lobu: Instructions file for Codex

AGENTS.md

lobu AGENTS.md is an instructions file for Codex, OpenCode from lobu-ai/lobu. It costs 2,997 tokens per session, scanned A, original, Apache-2.0.

A set of project instructions for working on the lobu codebase. It explains the repository layout, required setup process, restricted actions, and checks needed before shipping changes.

In plain words
What is it for?
Use it when modifying lobu packages, tests, submodules, or event data. It guides task setup, package-specific documentation checks, explicit staging, and comparison of changed files before a commit.
Why use it?
It reduces the risk of editing the wrong shared checkout, losing other work, or changing protected data and files unintentionally.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lobu-ai/lobu/agents-md.svg)](https://agentmods.dev/instructions/lobu-ai/lobu/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/lobu-ai/lobu/agents-md"><img src="https://agentmods.dev/badge/instructions/lobu-ai/lobu/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,997 This file is loaded in full into every session.
When invoked 2,997 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.02997 $0.02997
Opus 5 $0.01499 $0.01499
Sonnet 5 $0.00599 $0.00599
Haiku 4.5 $0.00300 $0.00300

Measured 7d ago against content hash 9bf5830b16e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

lobu 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 7d 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 · 66 lines

How it starts

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

Repo map

  • Bun workspace under packages/*; TS source in src, tests in __tests__.
  • core types/utils · plugin-api plugin contracts · plugin-host plugin composition · server gateway + embedded runtime · agent-worker agent execution · connectors built-in connectors · owletto frontend submodule.
  • Read the nearest package AGENTS.md before editing that package; grep docs/GOTCHAS.md when something looks inexplicable.

Unrecoverable — never do these

  • Never write to ~/Code/lobu directly. Run make task-setup NAME=<slug> first, and never git switch in the main checkout — other sessions share it. For a pure submodule-pointer bump, make bump SUBMODULE=packages/owletto is the lightweight isolated-worktree exception; it also posts the required statuses.
  • Stage by explicit path (git add -- <paths>, never -A). A commit is a snapshot, so a stale file copy left by earlier work in the same worktree silently reverts merged PRs. After commit/rebase, git diff --name-only origin/main...HEAD must equal your intended file list; extras = stop.
  • events is append-only. Never DELETE FROM events; tombstone or supersede instead.
  • Never bulk-delete prod organization rows, including zero-activity ones — empty-looking orgs are usually real signups. Surface them one at a time for confirmation.
  • Never resolve merge conflicts in the GitHub web UI — it has silently dropped 1000+ lines of feature work. Rebase locally against origin/main; submodule-pointer branches git merge instead (docs/GOTCHAS.md).
  • Two writing agents must never share a worktree — they overwrite each other's uncommitted work. Every subagent with Edit/Write/Bash gets its own through make task-setup (only task-setup does submodule pinning, bun install, .env copy, and port allocation); only read-only agents share the parent.
  • Never add a table or change DB design, API surface, or SDK surface without surfacing the proposal and receiving confirmation first.
  • Never auto-submit an interactive browser draft, in any package. Drafts are page-activated: persist the operation, notify normally, and let the extension activate the run only when the user visits a pending URL in a user-owned tab. Only scrape-owned scratch tabs may be opened and closed automatically. Server, connector, and Owletto code all obey this (packages/server/AGENTS.md).
  • Tenant/example state stays with its owner. Entity/relationship schemas, event kinds, Automations, prompts, agents, device pins, task IDs, and policies for one org, customer, project, or example belong in that example/config — never shared core, server, worker, SDK, or migrations. Before editing shared packages for an example, state the reusable platform invariant; if there is none, stop. Design-lock a genuinely missing public API/DB/cross-runtime contract as a separate PR.
  • Shared runtime never special-cases user entity keys. Only reserved $... entity types are platform-owned. All other semantics come from the entity schema or an explicit generic contract; an existing literal such as person or company is not precedent.
  • Connector logic stays connector-owned. Put it in the connector implementation or an explicitly named connector adapter/auth/webhook/migration module, registered through a generic contract. Never add connector-slug branches to otherwise generic runtime modules; extend the connector contract when the generic path lacks a capability.
  • Never commit live tenant identifiers or personal machine state. No real org UUIDs, entity/Automation/device/connection IDs, usernames, personal absolute paths, or task numbers in shipping code, shared migrations, or script defaults. Tenant state belongs in its example/config; tests use clearly synthetic values; operational scripts require explicit inputs.

Read the full file on GitHub · 66 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. 7d ago First seen · 66 lines · 2,997 tokens per session scan A 9bf5830b16e0

Subscribe to this mod's changes

lobu AGENTS.md is an instructions file published in the GitHub repository lobu-ai/lobu (217 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,997 tokens to every session, about $0.0150 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.

Related

Other instructions, from other repositories

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

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,182 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

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

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

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