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 decodingai-magazine/building-a-coding-agent-from-scratch-course --skill kitaru-adapter-buildergit clone --depth 1 https://github.com/decodingai-magazine/building-a-coding-agent-from-scratch-courseWrote 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/decodingai-magazine/building-a-coding-agent-from-scratch-course/kitaru-adapter-builder)<a href="https://agentmods.dev/skills/decodingai-magazine/building-a-coding-agent-from-scratch-course/kitaru-adapter-builder"><img src="https://agentmods.dev/badge/skills/decodingai-magazine/building-a-coding-agent-from-scratch-course/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/decodingai-magazine/building-a-coding-agent-from-scratch-course/kitaru-adapter-builder"><img src="https://agentmods.dev/badge/skills/decodingai-magazine/building-a-coding-agent-from-scratch-course/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.00079 | $0.01947 |
| Opus 5 | $0.00039 | $0.00974 |
| Sonnet 5 | $0.00016 | $0.00389 |
| Haiku 4.5 | $0.00008 | $0.00195 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- kitaru-adapter-builder — 100% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kitaru adapter builder
Build the smallest honest adapter inside the user's project. Preserve the framework's public entrypoint and report exactly what the 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.
- 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.
- 2d ago First seen · 193 lines · 79 tokens per session scan A a8ff7e1c070a
kitaru-adapter-builder is a skill published in the GitHub repository decodingai-magazine/building-a-coding-agent-from-scratch-course (387 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 1,947 once invoked, about $0.0004 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-09-09.
Other skills, from other repositories
review
Review a change for correctness, security, and missing tests.
hooks
Create and manage lifecycle hooks that vixd fires automatically on agent-loop events (a tool about to run, a prompt submitted, a thread starting, a turn finishing). Use when the user wants to enforce a rule, block or rewrite a tool call, validate prompts, auto-format, notify, or react to what the agent does.
jobs
Create and manage scheduled jobs (cron tasks, reminders, heartbeat checks, polling watchers) that vixd runs automatically. Use when the user asks to schedule, automate, monitor, watch, or be reminded about something.
workflow
Author and edit vix workflows — declarative multi-step pipelines (agent/bash/tool/if/fanout/fanin nodes) stored in config/workflow.json or embedded inline in a job/hook. Use when the user asks to create, modify, or understand a workflow, or to fan work out across many items and join the results.
review-pr
Deeply review a GitHub pull request.
vix-help
Answer questions about vix itself — the TUI (keybindings, tabs, threads, slash commands), configuration (settings.json, deny lists, permissions), agents & tools, models & providers, jobs, hooks, skills, workflows, MCP servers, the brain/code intelligence, headless/CLI usage, and installation. Use whenever the user…