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 amergrgic/kodama --skill kodama-behaviorgit clone --depth 1 https://github.com/amergrgic/kodamaWrote 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/amergrgic/kodama/kodama-behavior)<a href="https://agentmods.dev/skills/amergrgic/kodama/kodama-behavior"><img src="https://agentmods.dev/badge/skills/amergrgic/kodama/kodama-behavior/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/amergrgic/kodama/kodama-behavior"><img src="https://agentmods.dev/badge/skills/amergrgic/kodama/kodama-behavior.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.00037 | $0.00593 |
| Opus 5.5 | $0.00015 | $0.00237 |
| Sonnet 5.5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
kodama-behavior 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Behavior Playbook
Classify before acting
| Request shape | Default response |
|---|---|
| Single known edit or direct question | Act directly. |
| Repository discovery | Inspect existing code and tests before proposing changes. |
| Current API, framework, or compatibility question | Research primary sources. |
| Ambiguous outcome or missing constraint | Ask one focused clarification question. |
| Multi-step work | Define success criteria and a task list before editing. |
Delegate deliberately
Use a specialist when delegation improves quality or speed:
kodama-scout: repository structure, established patterns, dependencies, and tests.kodama-scholar: current external documentation and examples.kodama-sage: hard debugging, architecture, and high-impact tradeoffs.kodama-artist: user-facing UI, UX, accessibility, and interaction behavior.kodama-smith: application code, tests, and refactoring after scope is clear. Owns integration when a task spans domains — delegate to another specialist only for a substantial independent portion.kodama-critic: independent review of a non-trivial diff.kodama-forge: infrastructure, CI/CD, containerization, Docker, IaC, and deployment.kodama-scribe: documentation, changelogs, ADRs, and technical writing.
Every delegation must include: (1) Goal — one sentence; (2) Context — relevant paths and background; (3) Constraints — what is out of scope or disallowed; (4) Success criteria — observable conditions that prove completion.
Parallelize safely
Run investigation and research in parallel freely. Run implementation in parallel only when agents modify non-overlapping files or directories; otherwise, sequence implementation tasks. Reconcile findings before implementation.
Assess before modifying
Before changing unfamiliar code, identify:
- a similar implementation;
- local naming and organization conventions;
- dependencies already available;
- the relevant test location and test runner;
- the smallest safe validation command.
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.
- 1mo ago Changed · +8 lines 506aeea4a17f
- 1mo ago First seen · 51 lines · 37 tokens per session scan A b13dbb32ede3
kodama-behavior is a skill published in the GitHub repository amergrgic/kodama (11 stars, last pushed 16d ago), licensed MIT. It adds 37 tokens to every session and 593 once invoked, about $0.0001 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
kirocrew-app-dev
Build, package, and publish Kiro Crew external apps. Covers app.json manifests, UI components, crons, skills, lifecycle hooks, development mode, registry publishing, and common pitfalls.
goal-conductor
Own a goal too large for one session ('clear the flaky-test backlog', 'push N PRs green') end to end via the work ledger — decompose into items, one session per item, read worker status as data, verify claims with the acceptance evaluator, decide each round until done. Use when handed such a goal.
computer-use
Read and drive native desktop apps through the accessibility layer — list apps, snapshot a window as a numbered element tree, then click/type/scroll/drag by element index or screen coordinates. Use for a desktop app, not a web page. macOS + Windows; off unless enabled in Settings.
security-conductor
Operating procedure for the kirocrew-security-conductor agent. Use when a security conductor session is seeded, inspected or debugged. Run vulnerability discovery on one target as a supervised fleet — one auditor per attack surface, an independent verifier per finding, two human gates.
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
feature-demo-recording
Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…