Shared tokencheat report
Heuristic scoring — not financial advice.
Context efficiency score
85
Est. monthly savings (combined heuristics): $6
Findings
Caching coverage is 78% — reasonable.
Keep system prompts stable; avoid one-off prompt edits that bust cache.
Context footprint looks manageable.
Trim redundant examples; prefer smaller retrieval over stuffing everything in prompt.
MCP / tool volume is moderate.
Keep tool schemas tight; avoid returning full blobs when a digest suffices.
Model choice matches typical coding workloads.
Use a tiered model policy: router for simple edits, premium model for refactors.
System prompt size is reasonable.
Keep documenting changes in git, not in the prompt.
Structured retrieval active — agents read symbols, not entire files.
Keep jCodeMunch or equivalent indexed; re-index after large refactors.
The instruction file behind this score
# Project instructions ## Operating standard Assume technical fluency. Be concise and direct — prefer code, diffs, commands, and tables over prose. Run `pnpm test` and `pnpm type-check` before claiming any change is done, and report the actual output. Never fabricate packages, APIs, CLI flags, prices, or citations. State assumptions and blockers plainly. Search the repository for an existing implementation before writing a new one; extend the pattern you find. Check official documentation before answering anything version-dependent. ## Research and reuse Check official documentation and maintained sources before answering anything version-dependent. Introduce a new dependency only when the selected stack cannot do the job. Name what it adds. ## Approval gates Ask before production deploys, destructive migrations, or anything touching billing or auth. Read secrets from env only — never hardcode, echo, or log them. ## Agent use Use one agent for sequential work and bounded subagents for independent research or review. Never let parallel agents edit the same files; partition ownership by directory or worktree.
Stay in the loop
Get the '100 AI Coding Configs Analyzed' report
One email when our benchmark report drops — plus occasional context-efficiency findings. No spam.
No card, no spam. Your address is stored for the waitlist and nothing else — see the privacy policy.