Tokscale is a command-line tool and dashboard that records and analyzes token usage and costs across AI coding agents. Developers use it to monitor their consumption and optionally submit usage data to a shared leaderboard; the catalogue entry is an instruction for working with it.
Borrowing it
Nothing to install: this file belongs to junhoyeo/tokscale. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/junhoyeo/tokscale/main/AGENTS.mdgit clone --depth 1 https://github.com/junhoyeo/tokscaleWrote 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/junhoyeo/tokscale/agents-md)<a href="https://agentmods.dev/instructions/junhoyeo/tokscale/agents-md"><img src="https://agentmods.dev/badge/instructions/junhoyeo/tokscale/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.
<a href="https://agentmods.dev/instructions/junhoyeo/tokscale/agents-md"><img src="https://agentmods.dev/badge/instructions/junhoyeo/tokscale/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.03777 | $0.03777 |
| Opus 5.5 | $0.01511 | $0.01511 |
| Sonnet 5.5 | $0.00755 | $0.00755 |
| Haiku 4.5 | $0.00378 | $0.00378 |
Grade A, and why
tokscale 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- token-stats AGENTS.md — 95% identical, 25 lines differ
How it starts
The opening of the file, as written. The whole thing — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines
This document provides context for AI agents working on the Tokscale project.
Maintaining AGENTS.md Files
When updating AGENTS.md files, follow these principles:
- No hardcoded counts — Don't write "10 crates" or "5 modules"; these become outdated instantly
- No exhaustive lists — Prefer dynamic commands (
ls crates/) over maintaining complete lists - Document constraints, not descriptions — Focus on non-obvious behaviors, gotchas, and cross-crate dependencies
- Use nested AGENTS.md — Place crate-specific details in
crates/{name}/AGENTS.md, not here - Verify before documenting — Grep/read the code to confirm claims are accurate
- Delete outdated info — Outdated docs are worse than no docs
Authoring PR/Issue Content via gh CLI
When writing PR bodies, issue bodies, or comments through gh pr create, gh issue comment, etc.: prefer --body-file with a written-out file over inline --body heredocs.
Why: inline --body "$(cat <<'EOF' ... EOF)" patterns lead to recurring mistakes where backticks are written as \` (incorrectly escaping them inside a single-quoted heredoc where no escaping is needed). The literal \` then renders in GitHub markdown as backslash + backtick instead of inline code formatting.
DO:
- Write the body to
/tmp/pr-body.md(or similar) with theWritetool, thengh pr create --body-file /tmp/pr-body.md - For comment edits:
gh api -X PATCH repos/<owner>/<repo>/issues/comments/<id> -F body=@/tmp/comment.md
DON'T:
- Use
gh pr create --body "$(cat <<'EOF' ... \... ` ... EOF)"— single-quoted heredoc means backticks are already literal; escaping with `` \`` is wrong and renders incorrectly. - Use double-quoted heredoc for bodies containing backticks unless you intend command substitution.
- Hard-wrap paragraphs at ~80 columns inside PR/issue/comment bodies. GitHub's markdown collapses single newlines into spaces so the rendered output looks fine, but the raw markdown view is what reviewers and authors edit in, and mid-sentence line breaks read as if the prose was chopped. Write each paragraph as one continuous line and let the renderer wrap it. Same rule for blockquotes, list items that span multiple lines, and table cells. Hard wraps are still fine inside fenced code blocks where preserving line layout matters.
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.
- 9d ago Changed 24ae25c7dd46
- 1mo ago First seen · 283 lines · 3,777 tokens per session scan A dd62ff7dccf1
tokscale AGENTS.md is an instructions file published in the GitHub repository junhoyeo/tokscale (5,748 stars, last pushed yesterday), licensed MIT. It adds 3,777 tokens to every session, about $0.0151 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.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.