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 skills/luqueee/kivgraph/running-testsnpx skills add Luqueee/kivgraph --skill running-testsgit 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.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 | $0.00094 | $0.02910 |
| Opus 5 | $0.00047 | $0.01455 |
| Sonnet 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 3d 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.
- 3d ago First seen · 219 lines · 94 tokens per session scan A d95fc62d088c
running-tests is a skill published in the GitHub repository Luqueee/kivgraph (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 94 tokens to every session and 2,910 once invoked, about $0.0005 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
codestory-grounding
Use when an agent should ground a local repository with CodeStory before making source claims, planning edits, choosing tests, reviewing changes, or using broad retrieval evidence through the CodeStory plugin MCP.
graft
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
omnigraph
Store, retrieve, and query knowledge, memory, and relationships in an Omnigraph graph, and operate a local or remote Omnigraph deployment. Use when the user wants to capture or recall facts, notes, or entities, build or query a knowledge graph or agent memory, or run Omnigraph — and whenever you see Omnigraph CLI…
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
code-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
using-leankg
Code search via LeanKG MCP when HTTP :9699 is healthy; otherwise skip LeanKG and use default Grep/Glob/Read. Invoke before code navigation when LeanKG may apply.