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 skills add zenml-io/kitaru-skills --skill kitaru-adapter-buildergit clone --depth 1 https://github.com/zenml-io/kitaru-skillsWrote 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/zenml-io/kitaru-skills/kitaru-adapter-builder)<a href="https://agentmods.dev/skills/zenml-io/kitaru-skills/kitaru-adapter-builder"><img src="https://agentmods.dev/badge/skills/zenml-io/kitaru-skills/kitaru-adapter-builder/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/zenml-io/kitaru-skills/kitaru-adapter-builder"><img src="https://agentmods.dev/badge/skills/zenml-io/kitaru-skills/kitaru-adapter-builder.svg" alt="Reviewed on agentmods" width="80" 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.00084 | $0.02135 |
| Opus 5 | $0.00042 | $0.01068 |
| Sonnet 5 | $0.00017 | $0.00427 |
| Haiku 4.5 | $0.00008 | $0.00214 |
Grade A, and why
kitaru-adapter-builder 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 6d 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.
This is a copy
100% identical to kitaru-adapter-builder — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kitaru adapter builder
First select the smallest honest supported integration. Build an adapter inside the user's project only when no supported route meets the requested recording and replay boundary. Preserve the framework's public entrypoint and report exactly what the selected or custom adapter can observe, record, replay, and recover from.
Do not assume every framework can support the same fidelity. A useful result is either a locally tested adapter or a precise blocker tied to the installed versions and public hooks.
Core contract
- Start with read-only inspection of the user's project and installed packages.
- Prefer supported Kitaru adapters, importers, or OTLP export when they meet the requested recording and replay needs. Do not create a duplicate integration.
- For an already instrumented Python agent using Langfuse, Braintrust, LangSmith, Logfire, or Arize Phoenix, check the provider's importer-backed adapter before proposing custom code. Read the Python adapter reference for the package and capability contract.
- Treat the user's installed SDK and framework as authority. Use Kitaru reference adapters as patterns, not as source to copy or as proof of a published API.
- Use only public framework hooks. Offer a coarser boundary or stop when complete coverage would require private internals.
- Implement in the user's project first. Do not edit Kitaru core or prepare an upstream contribution unless the user separately approves that work.
- Keep per-run session IDs, clients, node indexes, buffers, replay state, and framework context isolated. Never store invocation state on a shared wrapper.
- Treat a partially recorded run as partial or failed evidence. Never call it a complete trace because the application returned successfully.
- Treat replay as execution, not a transaction. Block unknown or write-capable side effects unless the selected policy and user approval make them safe.
- Never install dependencies, call credentialed providers, create a remote Kitaru session, execute write-capable tools, or publish changes without the relevant approval.
- Run every Kitaru CLI command and SDK script with
KITARU_ACTIVE_SKILL=kitaru-adapter-builderset so the server attributes the resulting activity to this skill. - Start or restart a user-controlled worker with
--concurrency 10. UseKITARU_WORKER_CONCURRENCY=10only when the launch surface exposes worker settings through environment variables instead of CLI options.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed · +14 lines · +5 tokens per session 531bb0665e9d
- 11d ago First seen · 193 lines · 79 tokens per session scan A a8ff7e1c070a
kitaru-adapter-builder is a skill published in the GitHub repository zenml-io/kitaru-skills (4 stars, last pushed yesterday), licensed Apache-2.0. It adds 84 tokens to every session and 2,135 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to kitaru-adapter-builder, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
google-ads-audit
Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…