pub: Instructions file for Codex

AGENTS.md

pub AGENTS.md is an instructions file for Codex, OpenCode from xmanatee/pub. It costs 416 tokens per session, scanned A, original, MIT.

Project instructions for Pub, a full-stack TypeScript system for interfaces powered by AI agents, including its web app, command-line tool, relay services, and live app.

In plain words
What is it for?
They guide work across the monorepo, including its app, CLI, relay, live chat, canvas, tunnel, bridge, configuration, and generated files.
Why use it?
They help developers make changes in the correct system layer without overwriting user content or breaking privacy and cleanup rules.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xmanatee/pub/agents-md"><img src="https://agentmods.dev/badge/instructions/xmanatee/pub/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 416 This file is loaded in full into every session.
When invoked 416 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.00416 $0.00416
Opus 5.5 $0.00166 $0.00166
Sonnet 5.5 $0.00083 $0.00083
Haiku 4.5 $0.00042 $0.00042

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

Security

Grade A, and why

pub 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 · 44 lines

How it starts

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

Pub

Pub is a full-stack TypeScript system for adaptive interfaces powered by AI agents. The repo spans a web app, CLI, relay infrastructure, and an embedded live app experience.

Before broad work, read parent AGENTS.md files up to the mono root; nearest scoped instructions apply last.

Operating Principles

  • Treat the implementation, configuration schema, package scripts, and focused docs as the source of truth for exact commands, protocols, limits, and wiring.
  • Keep agent-facing guidance high level here; do not duplicate details that can be read directly from code, generated config, or narrower documentation.
  • Preserve user-owned workspaces and user-authored content. Initialization and upgrades must not silently overwrite local edits.
  • Keep live chat, canvas, tunnel, and bridge responsibilities separated. Do not route around the owning layer when changing delivery behavior.
  • Keep generated, vendored, and primitive UI surfaces read-only unless their owning workflow explicitly regenerates or updates them.
  • Follow existing routing, state, styling, and data-ownership patterns before introducing new abstractions.
  • Keep product privacy and cleanup invariants intact when adding creation, sharing, connection, or deletion behavior.
  • When public CLI or agent-facing behavior changes, keep the shipped runtime guidance and metadata in sync with the implementation.

Architecture Guidelines

  • Web, CLI, relay, and live-app code should remain loosely coupled through their existing boundaries.
  • The CLI owns local setup, validation, daemon lifecycle, bridge coordination, and tunnel startup. Keep those concerns explicit and observable.
  • The embedded live app is a starting point for user work. Once materialized in a workspace, treat it as user-owned source.
  • Feature work should be additive where possible and should keep feature-local concerns inside the feature boundary.
  • Prefer small, verifiable changes that preserve established conventions over broad refactors.

Read the full file on GitHub · 44 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 · 44 lines · 416 tokens per session scan A 1aadea411959

Subscribe to this mod's changes

pub AGENTS.md is an instructions file published in the GitHub repository xmanatee/pub (2 stars, last pushed 2d ago), licensed MIT. It adds 416 tokens to every session, about $0.0017 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.

Related

pub AGENTS.md compared with instructions from other repositories

pub AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pub AGENTS.mdxmanatee/pubInstructions file22d agoMITA416Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,649GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot