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/developerz-ai/universal-lsp/checkgit clone --depth 1 https://github.com/developerz-ai/universal-lspWhat 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.00014 | $0.00189 |
| Opus 5 | $0.00007 | $0.00095 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
check 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.
What it actually says
/check
bin/check --changed- If it passes and you are about to push:
bin/check(background if slow).
Stop at the first failure, fix it, re-run only that command.
Report one line per step: ✓ <label> or ✗ <label> — <error summary>.
Fix rules:
- Compiler warning → fix the code. Never add a suppression;
-Werroris on deliberately. - Guard violation → the message names the fix. Never an allowlist entry.
- Format →
bin/fmt. - Test failure → read the assertion before touching anything. Do not "fix" a test to match new behaviour unless the new behaviour is what was asked for.
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.
- yesterday First seen · 22 lines · 14 tokens per session scan A 9a72b222d366
check is a command published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 14 tokens to every session and 189 once invoked, about $0.0001 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-31.
Other commands, from other repositories
rb-ask
Ask a question about the current project's codebase via the repobrain knowledge hub. / 通过 repobrain 知识库询问当前项目代码。.
rb-refresh
Rebuild the repobrain project knowledge base after significant changes. / 在重要改动后重建 repobrain 项目知识库。.
coverage
Ingest or inspect test-coverage reports — LCOV, Cobertura/Clover, or coverage.py .coverage (builds the per-test map when contexts are present).
doctor
Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.
harden
Run the real-OSS harden harness against the 8 canary repos.
init
Set up Repowise for this codebase. Installs if needed, asks about your preferences, and runs the indexing.