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/zenml-io/kitaru/kitaru-tests-releasenpx skills add zenml-io/kitaru --skill kitaru-tests-releasegit clone --depth 1 https://github.com/zenml-io/kitaruWhat 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.02272 |
| Opus 5 | $0.00009 | $0.01136 |
| Sonnet 5 | $0.00003 | $0.00454 |
| Haiku 4.5 | $0.00002 | $0.00227 |
Grade A, and why
kitaru-tests-release 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kitaru Tests, CI, and Release Workflow
Use this when adding, moving, or debugging tests beyond the basic commands and safety rules in tests/AGENTS.md, or when changing CI/release behavior.
Unit and Contract Tests
- Build small typed stubs or
SimpleNamespaceobjects instead of booting unrelated runtime state. - Assert one behavior or contract at a time.
- Include regression coverage for bug fixes.
- Keep tests independent of working-directory state unless the test creates that state explicitly.
- Avoid shared mutable module-level state and wall-clock ordering assumptions.
V2 has no primed_zenml fixture or test_phase* example suite. Do not copy those v1 patterns into new tests.
CLI Tests
- Install the surface with
uv sync --extra cli --extra worker. - Call
src/kitaru/cli/app.py::mainwith an explicit argument list. - Assert the returned integer exit code, such as
main(["--help"]) == 0; successful calls do not raiseSystemExit(0). - Use
capsysand assert stable structured or plain-text contracts. - Prefer lightweight stubs for remote resources instead of starting the full server.
- Exercise offline help, version, schema, and scaffold commands without reading local configuration.
- Run
just cli-artifact-smokeafter optional-dependency, entrypoint, or packaging changes.
Keep CLI tests focused on argument parsing, command dispatch, output contracts, and the specific resource interaction under test.
Server and SDK Tests
Follow the four server-resource surfaces in tests/AGENTS.md: service tests, ASGI REST tests, shared repository contracts, and PostgreSQL end-to-end tests. Add SDK round-trip coverage under tests/client/ when a public resource changes.
Use the PostgreSQL-backed tests for transaction, locking, migration, or cross-request behavior that an in-memory fake cannot prove. Run docker compose up -d db before those tests and just migration-check after schema changes.
Task and Worker Tests
- Task subprocess contracts live under
tests/task/. - Worker lifecycle and handler contracts live under
tests/worker/. - Keep subprocess tests bounded and assert structured receipts, exit behavior, and redaction.
- Use the existing worker fakes rather than starting unrelated services.
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 · 134 lines · 17 tokens per session scan A f5e8594e2db4
kitaru-tests-release is a skill published in the GitHub repository zenml-io/kitaru (270 stars, last pushed 4d ago), licensed Apache-2.0. It adds 17 tokens to every session and 2,272 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-30.
Other skills, from other repositories
migrating-world-v4-to-v5
Upgrades a custom Workflow SDK World implementation from the v4 spec to v5. Use when a package implements the World interface from @workflow/world and is moving to 5.x — event IDs that are ULIDs rather than slot positions, Event id is not slot-numbered at replay time, a specVersion the runtime refuses, writeToStream /…
field-descriptions
Write or review Pydantic Field(description=...) text for ZenML stack component configs. Use when adding, editing, or reviewing config fields in src/zenml/integrations//flavors/ or any StackComponentConfig subclass, or when scripts/validatedescriptions.py fails.
workflow-init
Install and configure Vercel Workflow SDK before it exists in nodemodules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, or Vite.
experiment-tracking-swanlab
Provides guidance for experiment tracking with SwanLab. Use when you need open-source run tracking, local or self-hosted dashboards, and lightweight media logging for ML workflows.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
mlflow
Track ML experiments, manage model registry with versioning, deploy models to production, and reproduce experiments with MLflow - framework-agnostic ML lifecycle platform.