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.
npx agentmods add commands/agentis-tools/ctx/lspgit clone --depth 1 https://github.com/agentis-tools/ctxWhat 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 | $0.00000 | $0.03047 |
| Opus 5 | $0.00000 | $0.01523 |
| Sonnet 5 | $0.00000 | $0.00609 |
| Haiku 4.5 | $0.00000 | $0.00305 |
Grade A, and why
lsp 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctx lsp
Manage LSP-backed language support from the community registry.
Synopsis
ctx lsp add <LANGUAGE> [--server <NAME>] [--yes] [--json]
ctx lsp list [--available] [--json]
ctx lsp update [LANGUAGE] [--yes] [--json]
ctx lsp doctor [--json]
Description
The lsp command manages [lsp.<language>] blocks in .ctx/config.toml — the declarative registrations that let ctx index extract symbols through any stdio language server (see Add a language via LSP). add installs a curated entry from the community LSP registry, list shows what is configured (or available), update refreshes registry-installed entries, and doctor health-checks every configured server.
The registry lives in a separate repository, agentis-tools/ctx-lsp-registry. ctx fetches its raw TOML manifests over HTTPS from the pinned v1 branch (10-second timeout per fetch). Entries whose schema_version is newer than the running binary understands are rejected with a message telling you to upgrade ctx.
Trust model
ctx lsp add never executes anything. It writes a TOML block to .ctx/config.toml — nothing else:
- The command, arguments, install hint, and homepage from the registry are shown to you first, and nothing is written until you confirm (
--yesskips the prompt). - The install hint (e.g.
npm install -g pyright) is printed for you to run yourself; ctx never installs a server. - The server binary itself is only ever executed later, by
ctx index(when a matching file is indexed) or byctx lsp doctor(as an explicit health probe). - Hand-written
[lsp.<language>]entries are never touched:addrefuses to overwrite them andupdaterefuses to refresh them. Only entries carrying thesource = "registry"provenance key are managed by these commands. - Config writes are format-preserving and atomic: comments, formatting, and unrelated tables in
.ctx/config.tomlsurvive byte-for-byte.
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.
- 2d ago First seen · 250 lines · 0 tokens per session scan A 5bf5d9fe067a
lsp is a command published in the GitHub repository agentis-tools/ctx (11 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,047 tokens. 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 commands, from other repositories
coograph-review
Review the changes in scope for spec compliance, convention violations, logic bugs, and architectural issues. You review — you do not author. Never edit files.
coograph-verify
Verify that the described work is complete and correct. Provide evidence for every claim. You verify — you do not implement or fix style.
api-gen
Generate REST API endpoints with routes, validation, error handling, and tests.
component-gen
Generate React or Vue components with prop types, styling, accessibility, and tests.
code-review
Review staged git changes for bugs, security issues, and style violations.
pr-description
Generate a PR title and description from the current branch diff against main.