Borrowing it
Nothing to install: this file belongs to developerz-ai/universal-lsp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/developerz-ai/universal-lsp/main/.claude/skills/build-and-test/SKILL.mdgit clone --depth 1 https://github.com/developerz-ai/universal-lspWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/developerz-ai/universal-lsp/build-and-test)<a href="https://agentmods.dev/skills/developerz-ai/universal-lsp/build-and-test"><img src="https://agentmods.dev/badge/skills/developerz-ai/universal-lsp/build-and-test.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00061 | $0.00523 |
| Opus 5 | $0.00030 | $0.00262 |
| Sonnet 5 | $0.00012 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
build-and-test 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 5d 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.
What it actually says
Build and test
Which command
| Question | Command |
|---|---|
| did my edit format + pass the guards? | bin/check --files <paths> |
| do the subsystems I touched still pass? | bin/check --changed |
| is the repo green? (once, before push) | bin/check |
| build only | bin/dev build [dev|asan|release] |
| one test | bin/dev test <regex> |
| memory bugs | bin/dev asan |
| environment wrong? | bin/dev doctor |
Never hand-roll a cmake invocation a preset covers. Never trust a piped exit
code — cmd \| tail; echo $? reports tail's status.
Failure → fix
| Symptom | Do |
|---|---|
No tests were found |
build first (bin/dev test does), and register via ulsp_add_test, not bare add_test |
| clangd cannot find a header | bin/setup symlinks compile_commands.json |
| a warning fails the build | fix the code. -Werror is deliberate; never add a suppression |
| ASan reports a use-after-free | read the allocation trace, not just the free — arena/pmr lifetimes are the usual cause |
| a guard fires | the message names the fix. Never an allowlist entry |
| green locally, red in CI | the parity bug: fix scripts/lib/gate.ts and .github/workflows/ci.yml together, then bun test scripts/ |
Adding a suite
ulsp_add_test(engine_offsets_test
SOURCES offsets_test.cpp
LINK ulsp::engine)
Name it <subsystem>_* — scripts/lib/affected.ts maps subsystem to CTest regex
by prefix, so a differently-named suite silently stops being selected by the
scoped tier.
Details: docs/standards/testing.md, docs/standards/dev-loop.md.
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.
- 5d ago First seen · 48 lines · 0 tokens per session scan A 730ec502be11
build-and-test is a skill published in the GitHub repository developerz-ai/universal-lsp (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 61 tokens to every session and 523 once invoked, about $0.0003 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 skills, from other repositories
cpp-project-setup
Modern C++ project setup: CMake/CMakePresets, vcpkg, Ninja, VS Code/clangd, GoogleTest, clang-format/tidy, Doxygen, CI, macOS/Linux/Windows. Use for bootstrapping or modernizing host-side C++ apps and libraries; prefer embedded-project-setup for MCU firmware and cross-debug flows.
cpp-mentor
A general, self-adapting C++ mentor for any project. On first run with an empty profile it onboards: settles the goal and domain, derives a namespace from the goal, agrees conventions, and audits the developer's level in both C++ and the project's topic — then saves a per-project profile and calibrates to it. On…
transform-model
Use when onboarding a Hugging Face model into TensorRT-Model-Connect or extending an existing family to produce a .bundle bundle. Drives ownership-first implementation across Python builder, native runtime, and model-owned E2E descriptors, then requires reference-consistency and runtime evidence before support is…
readable-cpp
Readable C/C++/Rust/CUDA code rules inspired by The Art of Readable Code. Use when writing, reviewing, or refactoring C, C++, Rust, or CUDA code. Enforces short functions, flat control flow, clear naming, readable structure, and idiomatic patterns.
tlaplus-spec-generator
Automatically generate TLA+ specifications from source code (C/C++, Python) for formal verification of distributed systems. Use when users need to: (1) Generate TLA+ specs from program implementations, (2) Model distributed systems, consensus protocols, or concurrent algorithms, (3) Extract state variables, actions…
acsl-annotation-assistant
Create ACSL (ANSI/ISO C Specification Language) formal annotations for C/C++ programs. Use this skill when working with formal verification, adding function contracts (requires/ensures), loop invariants, assertions, memory safety annotations, or any ACSL specifications. Supports Frama-C verification and generates…