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/featuregit 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.00017 | $0.00499 |
| Opus 5 | $0.00009 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
feature 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
/feature
Done means merged and verified. A green local gate is not done; an open PR is not done.
Goal
$ARGUMENTS
Steps
- Restate the goal in one line. If two readings exist, say so before building.
- Distrust the paperwork. If working from a plan or a doc, check it against
the code and
git logfirst — trackers rot in both directions. State plainly which claims you falsified and fix the doc in the same change. - Explore in parallel, read-only, into a ranked worklist of PR-sized batches.
- Test first. Bug → reproducing test. Feature → the assertion that defines
done. Register suites with
ulsp_add_test, named<subsystem>_*. - Build the smallest correct thing. One primitive with its first real caller; no abstraction before a second consumer exists.
- Verify by tier:
bin/check --files <paths>after each edit,bin/check --changedwhen the slice compiles,bin/checkonce before pushing. Fail one, fix one — re-run only the failing command. - PR:
<type>/<slug>branch, conventional commit,Closes #N, one concern, ~110 files max. Never push red; wait for checks to register. - Merge queue depth 1. Never two PRs in flight — each merge rebases
mainunder the other and CI results go stale silently.
Fan-out
One checkout. No git worktrees — work lands in a directory nobody is looking
at, and each one needs its own configure and build tree. Brief every agent with
its exclusive paths, concurrency 1, no git operations, never git stash.
Stop for
An irreversible action, a change to a public contract (the LSP surface, MCP tool
names, graph-lite.h, the persistence format), or anything that would need a
guard disabled. Those are decisions, not steps.
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 · 45 lines · 17 tokens per session scan A 1f34cf1b80fb
feature is a command published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed 10d ago), licensed Apache-2.0. It adds 17 tokens to every session and 499 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.