Borrowing it
Nothing to install: this file belongs to Luqueee/kivgraph. 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/Luqueee/kivgraph/main/.claude/skills/running-tests/SKILL.mdgit clone --depth 1 https://github.com/Luqueee/kivgraphWrote 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/luqueee/kivgraph/running-tests)<a href="https://agentmods.dev/skills/luqueee/kivgraph/running-tests"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/running-tests/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/luqueee/kivgraph/running-tests"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/running-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.02910 |
| Opus 5.5 | $0.00038 | $0.01164 |
| Sonnet 5.5 | $0.00019 | $0.00582 |
| Haiku 4.5 | $0.00009 | $0.00291 |
Grade A, and why
running-tests 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 2mo 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ejecutar los tests de Kivgraph
La regla que más cuesta descubrir
Nunca go test -tags ladybug. Falla al enlazar:
ld: library 'lbug' not found
No falta la biblioteca: falta decirle al enlazador dónde está. make test-ladybug
exporta las variables CGO_* que apuntan a .tooling/ladybug/<versión>, pasa el
rpath por -ldflags y es el único modo soportado de ejecutar ese tag.
make test-ladybug # suite completa con la capa nativa
make test-ladybug PKGS=./internal/storage/ladybug # un paquete mientras se trabaja
scripts/fetch-ladybug.sh descarga y verifica la biblioteca la primera vez; el
target lo invoca solo. Queda un aviso por binario, y es del binding: el -L
que apunta a su propio directorio de módulo no existe en un build fijado.
Silenciarlo exigiría parchear un módulo fijado por digest.
Los avisos duplicate -rpath y ignoring duplicate libraries ya no salen. Eran
221 en una pasada completa y ninguno era un defecto: CGO_LDFLAGS se aplica a
cada paquete cgo en vez de una vez al enlazar, así que nombrar ahí -llbug o el
rpath -- que el binding ya declara -- hacía que el enlazador viera diez copias de
cada uno. Si vuelven, es que alguien los devolvió a CGO_LDFLAGS.
Las tres suites
| Comando | Cubre | Ejecutando | Con caché |
|---|---|---|---|
go test ./... |
34 paquetes; toda la lógica que no toca LadybugDB nativo | 20 s |
0.6 s |
make test-ladybug |
39 paquetes con -tags ladybug |
45 s |
47 s |
pnpm check en ts-worker/ y en web/ |
formato, lint, tipos y vitest (87 y 69 tests) |
3 s cada uno |
igual |
La primera invocación de make test-ladybug tarda unos 150 s: compila cgo
desde cero. Después el coste es el de ejecutar, y la caché de test no lo baja
porque el enlazado con la biblioteca nativa se rehace igual.
go test ./... no compila los archivos con //go:build ladybug: son 22
archivos con 75 tests que la suite corriente no ve, repartidos en
internal/storage/ladybug, internal/indexer, internal/app e
internal/resilience, más cinco paquetes de benchmark que solo existen bajo el
tag. Esos paquetes salen ok sin el tag -tienen además tests que no lo
necesitan-, así que un verde no dice nada sobre ellos. Un cambio en
almacenamiento, indexación, rebuild, snapshots o apagado no está probado
hasta que pasa make test-ladybug.
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.
- 2mo ago First seen · 219 lines · 94 tokens per session scan A d95fc62d088c
running-tests is a skill published in the GitHub repository Luqueee/kivgraph (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 94 tokens to every session and 2,910 once invoked, about $0.0004 per session on Opus 5.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
codestory-grounding
Use when discovering repository structure, tracing relationships, analyzing change impact, or validating CodeStory retrieval or an installed plugin through the CodeStory plugin MCP. Skip only for bounded inspection or editing of named files that does not require those operations.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
potpie-project-preferences
Use before writing, modifying, reviewing, refactoring, or testing code so repo/project preferences surface: error handling, file structure, frameworks, logging, dependency choices, testing, security, API style, and naming. Also use after code work when a reusable project preference should be recorded.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
lsp-refactor
End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.
ring:verifying-code
Verifying a Go project: runs every quality check (lint, vet, imports, format, docs, unit, integration, E2E) and returns a single MERGEREADY or NEEDSFIX verdict. Report-only: never fixes anything. Use for a quick pre-merge or pre-PR check outside a full dev-cycle. Skip when not a Go project, when you want a single…