Token Tracker is a local-first dashboard and desktop application that records AI token usage and costs across coding tools. It is for developers who want to monitor their coding-tool consumption, model usage, rate limits, and spending without relying on a cloud account.
Borrowing it
Nothing to install: this file belongs to xiufengsun/TokenTracker. 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/xiufengsun/TokenTracker/main/AGENTS.mdgit clone --depth 1 https://github.com/xiufengsun/TokenTrackerWrote 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/xiufengsun/tokentracker/agents-md)<a href="https://agentmods.dev/instructions/xiufengsun/tokentracker/agents-md"><img src="https://agentmods.dev/badge/instructions/xiufengsun/tokentracker/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/xiufengsun/tokentracker/agents-md"><img src="https://agentmods.dev/badge/instructions/xiufengsun/tokentracker/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.00450 | $0.00450 |
| Opus 5.5 | $0.00180 | $0.00180 |
| Sonnet 5.5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
TokenTracker 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 1mo 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.
What it actually says
Agent Instructions
Use CLAUDE.md as the single source of truth for this repository's project guidance, architecture notes, release workflow, and conventions.
If any project-specific instructions appear to conflict across files, follow CLAUDE.md and update this file only to keep that pointer intact.
InsForge backend
This project uses InsForge: an all-in-one, open-source Postgres-based backend (BaaS) that gives this app a database, authentication, file storage, edge functions, realtime, an AI model gateway, and payments through one platform.
- Project: tokentracker (API base
https://srctyff5.us-east.insforge.app) - Skills: these InsForge skills are installed for supported coding agents. Reach for them before implementing any InsForge feature instead of guessing the API:
insforge: app code with the@insforge/sdkclient (database CRUD, auth, storage, edge functions, realtime, AI, email, and Stripe payments).insforge-cli: backend and infrastructure via theinsforgeCLI (projects, SQL, migrations, RLS policies, storage buckets, functions, secrets, payment setup, schedules, deploys).insforge-debug: diagnosing failures (SDK/HTTP errors, RLS denials, auth and OAuth issues) and running security or performance audits.insforge-integrations: wiring external auth providers (Clerk, Auth0, WorkOS, Better Auth, etc.) for JWT-based RLS, or the OKX x402 payment facilitator.find-skills: discovering additional skills on demand.
- Credentials: app code reads keys from
.env.local; the CLI reads.insforge/project.json. Never hardcode or commit keys.
Key patterns:
- Database inserts take an array:
insert([{ ... }]). - Reference users with
auth.users(id); useauth.uid()in RLS policies. - For storage uploads, persist both the returned
urlandkey.
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.
- 1mo ago First seen · 27 lines · 450 tokens per session scan A 413ababe6318
TokenTracker AGENTS.md is an instructions file published in the GitHub repository xiufengsun/TokenTracker (2,143 stars, last pushed today), licensed MIT. It adds 450 tokens to every session, about $0.0018 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.