context-tools

A set of tools for collecting and searching information while keeping large raw files out of the conversation. It can process files, run sandboxed code, index text, and fetch web pages.

In plain words
What is it for?
Use it to inspect logs and documents, search indexed content, run analysis, and retrieve the main text from web pages.
Why use it?
It reduces clutter when working with large files or many sources and makes useful passages easier to find again.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/hoangp8/tokless/context-tools
Clone the repo
git clone --depth 1 https://github.com/HoangP8/tokless

Made for: Cursor.

Per session 582 This file is loaded in full into every session.
When invoked 582 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00582 $0.00582
Opus 5 $0.00291 $0.00291
Sonnet 5 $0.00116 $0.00116
Haiku 4.5 $0.00058 $0.00058

Measured yesterday against content hash 713e1e8e5417, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

context-tools 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 yesterday.

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.

.cursor/rules/context-tools.mdc · 58 lines

What it actually says

Context Tools (context-mode)

Sandbox-first tools. Derive answers. Keep raw bytes out, print only needed results.

Use ctx?
├─ YES → source >~200 lines/KB, multi-source, or worth re-querying → prioritize ctx tools
└─ NO  → small file, single section, or verbatim-read for editing → Read directly
Tool Role Replaces
ctx_execute Run code in sandbox. Only stdout enters context. Bash for analysis tasks
ctx_execute_file Process file in sandbox. Raw bytes never leave. Read on large files (>200 lines)
ctx_batch_execute Run N commands + auto-index output. Search in same call. Concurrency 1-8. Multiple Bash + grep
ctx_index Chunk markdown/text into FTS5. Queryable via ctx_search. Manual grep over pasted content
ctx_search Multi-strategy search across indexed content + session memory. Typo correction. Re-asking user, re-deriving
ctx_fetch_and_index Fetch URL → markdown → index. Cache 24h (override ttl). Batch with requests+concurrency. WebFetch + re-read

Examples:

ctx_execute(language:"shell", code:"grep -rn 'TODO' src/ | head -20")
ctx_execute_file(path:"app.log", language:"javascript", code:`
  const lines = FILE_CONTENT.split('\\n');
  const errs = lines.filter(l => /ERROR|FATAL/.test(l));
  console.log(errs.length + ' errors');
  console.log(errs.slice(-5).join('\\n'));
`)
ctx_batch_execute(commands:[
  {label:"diff", command:"git diff HEAD~1"},
  {label:"status", command:"git status"},
  {label:"tests", command:"npm test 2>&1 | tail -20"},
], queries:["failures","errors"])
ctx_fetch_and_index(requests:[
  {url:"https://docs.example.com/api", source:"api-docs"},
  {url:"https://docs.example.com/guide", source:"guide"},
], concurrency:4)
ctx_search(queries:["auth endpoint","rate limits"], source:"api-docs")

Shell stays for git, mkdir, rm, mv, installs, tests. Write/Edit for file changes; ctx subprocess writes aren't host edits.

Windows: pwsh -NoProfile -Command, absolute paths, X:\ maps to /x/, quote spaces.

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.

  1. yesterday First seen · 58 lines · 582 tokens per session scan A 713e1e8e5417

Subscribe to this mod's changes

context-tools is a cursor rule published in the GitHub repository HoangP8/tokless (258 stars, last pushed yesterday), licensed MIT. It adds 582 tokens to every session, about $0.0029 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.