What is tokenless AGENTS.md?

Repository instructions for the tokenless project, covering its coding language, documentation style, tokenless feature, branches, and releases. They also define English and Simplified Chinese language requirements.

Use them when developing or documenting tokenless, especially when changing user-facing text or maintaining its English and Chinese documentation.

They give an agent the project-specific rules for code, documentation, localization, and release work.

How jazelly/tokenless configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to jazelly/tokenless. 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/jazelly/tokenless/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/jazelly/tokenless

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/jazelly/tokenless/agents-md/github.svg)](https://agentmods.dev/instructions/jazelly/tokenless/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/jazelly/tokenless/agents-md"><img src="https://agentmods.dev/badge/instructions/jazelly/tokenless/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/jazelly/tokenless/agents-md"><img src="https://agentmods.dev/badge/instructions/jazelly/tokenless/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,558 This file is loaded in full into every session.

When invoked 2,558 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.

Model	Per session	Once invoked
Fable 5.1	$0.02558	$0.02558
Opus 5.5	$0.01023	$0.01023
Sonnet 5.5	$0.00512	$0.00512
Haiku 4.5	$0.00256	$0.00256

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

Security

Grade A, and why

tokenless 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 · 102 lines

How it starts

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

Repository Development Rules

Language

Use English for code, identifiers, package/config keys, and inline comments.
Never use Tokenless alone when naming a product or architecture tier. Use Tokenless API for the provider-access API, daemon, CLI, and configuration in this repository, and Tokenless Harness for the agent runtime that consumes it. Prefer an even more specific subsystem name when relevant; exact identifiers and quoted product names are exempt.
Localize every reasonable user-facing surface in both English and Simplified Chinese. Never ship one language alone or assume users know the other.
Keep commands, flags, identifiers, protocol fields, provider/model names, and clearer technical terms unchanged.
Keep language selection and fallback consistent; cover externally visible localization through real boundaries.
Keep paired docs, such as README.md and README.zh-CN.md, structurally and semantically aligned.
Internal technical docs may remain English when translation adds no user value.

Documentation style

Do not ship walls of text. Keep paragraphs to one to three short sentences, and use a list, table, diagram, or screenshot when it makes the same point faster.
Keep product READMEs as scannable landing pages: lead with the value proposition and product visual, then show providers, quick start, and links to deeper documentation.
Put detailed reference material in the focused document that owns it and link there instead of duplicating long explanations.
Prefer one clear sentence over a section, and a few concrete bullets over a paragraph that merely enumerates features or steps.
Label illustrative or staged screenshots and metrics so they cannot be mistaken for benchmarks or production telemetry.

Production configuration boundary

Production behavior controls must be read from the persisted Tokenless API config.json, not from .env or process-environment overrides.
.env is reserved for test/bootstrap selectors such as TOKENLESS_TEST_HOME; it may locate the complete test home but must not override production behavior defined inside that home.
When a production setting needs to change, update the selected Tokenless API config through the supported configuration path. Do not add an environment-variable escape hatch.

Read the full file on GitHub · 102 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.

2mo ago Changed · +12 lines · +648 tokens per session b895c7584ec1
2mo ago First seen · 90 lines · 1,910 tokens per session scan A 6cbe104f8383

Subscribe to this mod's changes

tokenless AGENTS.md is an instructions file published in the GitHub repository jazelly/tokenless (16 stars, last pushed 1mo ago), licensed MIT. It adds 2,558 tokens to every session, about $0.0102 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-30.

agentic-ai ai-agents ai-tools anti-detect playwright web-harness

tokenless AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
tokenless AGENTS.mdjazelly/tokenless	Instructions file	16	1mo ago	MIT	A	2,558	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

tokenless: Instructions file for Codex