Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/benedict2310/telepi/agents-mdgit clone --depth 1 https://github.com/benedict2310/TelePiWrote 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.
[](https://agentmods.dev/instructions/benedict2310/telepi/agents-md)<a href="https://agentmods.dev/instructions/benedict2310/telepi/agents-md"><img src="https://agentmods.dev/badge/instructions/benedict2310/telepi/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01049 | $0.01049 |
| Opus 5 | $0.00524 | $0.00524 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
Grade A, and why
TelePi 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/ contains the runtime code. The main entrypoints remain src/index.ts, src/cli.ts, and src/bot.ts, while larger subsystems now live in focused subdirectories: src/bot/ holds Telegram transport/rendering/state/prompt helpers plus grouped command handlers under src/bot/commands/, and src/install/ holds installed-mode config, extension, launchd, and shared install helpers. Core session/model/voice logic still lives in top-level modules such as src/pi-session.ts, src/model-scope.ts, src/tree.ts, and src/voice.ts. test/ mirrors that structure: top-level integration suites such as test/bot.test.ts, test/install.test.ts, and test/pi-session.test.ts are backed by focused unit suites under test/bot/. Integration assets live beside the app: extensions/telepi-handoff.ts for Pi CLI hand-off, launchd/com.telepi.plist for macOS service setup, and Dockerfile plus docker-compose.yml for containerized runs.
Build, Test, and Development Commands
Use npm install to install dependencies. npm run dev starts TelePi with tsx against src/index.ts for local development. npm run build compiles TypeScript into dist/. npm start runs the built app from dist/index.js. npm test runs the Vitest suite once, and npm run test:coverage enforces coverage thresholds. For Docker, use docker compose up --build after creating .env.
Operational Commands
For the installed macOS launchd flow, rebuild from the repo root with npm run build. Restart the installed bot with launchctl kickstart -k gui/$UID/com.telepi. Check installed-mode status with node dist/cli.js status (or telepi status when the global CLI is on PATH). Installed-mode logs live under ~/Library/Logs/TelePi/.
Coding Style & Naming Conventions
This project uses strict TypeScript with ESM modules. Follow the existing style: 2-space indentation, double quotes, semicolons, and explicit .js import suffixes in TypeScript source. Prefer small, focused modules in src/ and keep filenames lowercase with hyphens only when already established, for example pi-session.ts and model-scope.ts. Export named functions and types where practical; avoid default exports unless there is a clear single entrypoint.
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.
- 4d ago First seen · 26 lines · 1,049 tokens per session scan A 0e8574f87900
TelePi AGENTS.md is an instructions file published in the GitHub repository benedict2310/TelePi (136 stars, last pushed 8d ago), licensed MIT. It adds 1,049 tokens to every session, about $0.0052 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.
Other instructions, from other repositories
Lucarne AGENTS.md
Instructions for tuchg/Lucarne, covering agent instructions, provider responsibility boundary, development and testing, release process and provider boundaries.
pi-fabric AGENTS.md
AGENTS.md instructions for monotykamary/pi-fabric, covering agents.md, golden rule: build when done, before committing, incremental checks while iterating and package manager.
my-pi AGENTS.md
Instructions for spences10/my-pi, covering agents.md, orientation, repository-specific skills, source of truth order and commit and changeset ownership.
LaPis AGENTS.md
Instructions for GeneGulanesJr/LaPis, covering protocols, 1. code & doc retrieval — use memory-code / memory-doc, 2. persistent memory — automatic, when to use the tools and content format.
pi-ask AGENTS.md
Instructions for eko24ive/pi-ask, covering agents.md, project scope, project goals, tech stack and commands.
pi-server AGENTS.md
Instructions for tryingET/pi-server, covering agents.md — crystallized learnings for pi-server, canonical references, architecture principles, adr-0001: atomic outcome storage and the invariant.