dexgram: Instructions file for Codex

AGENTS.md

dexgram AGENTS.md is an instructions file for Codex, OpenCode from yashau/dexgram. It costs 1,829 tokens per session, scanned A, original, MIT.

Project instructions for Dexgram, a Windows program that connects Telegram conversations to Codex Desktop coding sessions. Telegram topics are separate conversation threads, while one shared Codex process handles the sessions.

In plain words
What is it for?
Use it when changing Telegram topic routing, Codex session attachment, side chats, Windows process cleanup, or the project’s development commands.
Why use it?
It explains how messages, approvals, side chats, and existing sessions must be routed so conversations do not get mixed up.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/yashau/dexgram/agents-md"><img src="https://agentmods.dev/badge/instructions/yashau/dexgram/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,829 This file is loaded in full into every session.
When invoked 1,829 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.01829 $0.01829
Opus 5.5 $0.00732 $0.00732
Sonnet 5.5 $0.00366 $0.00366
Haiku 4.5 $0.00183 $0.00183

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

Security

Grade A, and why

dexgram 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 · 202 lines

How it starts

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

AGENTS.md

Guidance for agents working on Dexgram.

Project Overview

Dexgram is a Windows-only Telegram bridge for Codex Desktop. It runs as a Go binary, listens through a Telegram bot with threaded topics enabled, and maps Telegram topics to Codex app-server threads.

Dexgram owns one shared Codex app-server --listen stdio:// process per Dexgram runtime. Topic sessions are routing records over that shared client, not one app-server per Telegram topic. Events and approval/user-input requests must be routed by Codex threadId/turnId to the mapped Telegram topic. The shared app-server is tracked with a small PID marker and guarded by a Windows Job Object so stale children are cleaned up after crashes or restarts.

Side chats are Telegram topics created with /side or /btw. They are backed by native Codex thread/fork, keep the same project/cwd as the parent, and use a ↳N topic-name prefix so they do not get confused with the main topic.

Existing Codex sessions can be attached to Telegram topics through /sessions [query]. The browser lists projects first, then paginated threads inside a selected project. Attaching a session maps that topic to the existing Codex thread and syncs up to the most recent 25 rendered Telegram history messages.

Fresh unbound topics must not silently become projectless chats on the first prompt. Dexgram should first ask whether to resume an existing session, start a new chat, or set a project first.

The main command lives in cmd/dexgram. Shared packages live under internal/:

  • internal/codex: Codex app-server JSON-RPC client.
  • internal/codexprojects: Codex Desktop project discovery.
  • internal/codexstate: projectless workspace helpers.
  • internal/config: TOML config loading/defaults.
  • internal/state: SQLite-backed mapping, sync, settings, and pairing-code state.

Keep changes small and aligned with the current layout. Prefer local helpers and existing package boundaries over adding new framework-like abstractions.

Read the full file on GitHub · 202 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 · 202 lines · 1,829 tokens per session scan A 89d1c8792499

Subscribe to this mod's changes

dexgram AGENTS.md is an instructions file published in the GitHub repository yashau/dexgram (8 stars, last pushed 4mo ago), licensed MIT. It adds 1,829 tokens to every session, about $0.0073 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

dexgram AGENTS.md compared with instructions from other repositories

dexgram AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
dexgram AGENTS.mdyashau/dexgramInstructions file84mo agoMITA1,829Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode