kimi-agent-policy

# kimi-agent-policy

Kimi agent tool-use policy and behavior rules, adapted for OpenClaw.
Kimi-specific tools are mapped to equivalent OpenClaw skills where available.

## Trigger Conditions

- Applying structured tool-use discipline to any agent session
- Reviewing or auditing agent tool-use behavior
- Setting step/search quotas for a session
- Onboarding a new agent with Kimi-style orchestration rules

---

## Tool Mapping (Kimi → OpenClaw)

| Kimi Tool | OpenClaw Equivalent | Skill | API Key? |
|-----------|-------------------|-------|----------|
| `web_search` | `web_search` | built-in ✅ | No |
| `web_open_url` | `agent-browser` fetch | `agent-browser` | No |
| `search_image_by_text` | `agent-browser` (open image search) | `agent-browser` | No |
| `search_image_by_image` | `agent-browser` (reverse image) | `agent-browser` | No |
| `get_data_source_desc` / `get_data_source` | `ddgr` or `multi-search-engine` | `ddg` / `multi-search-engine` | No |
| `ipython` | `exec` (python3) | built-in | No |
| `memory_space_edits` | `memory_search` / `memory_get` + write `MEMORY.md` | built-in | No |

> All replacements are free and require no API keys.

---

## 1. Step & Search Limits

Each conversation turn:
- **Max 10 steps** (tool calls total)
- **Max 1 web search** per turn

If a task genuinely requires more, split across turns.

---

## 2. Web Tools

### `web_search` (built-in) or `ddgr` (`ddg` skill, no API key)

Fallback priority:
1. `web_search` built-in
2. `ddgr` — DuckDuckGo CLI, privacy-focused, no API key
3. `multi-search-engine` — 17 engines (Baidu/Google/Bing/DDG etc), no API key

Use when:
- Data changes frequently (prices, news, events)
- Unfamiliar entity or concept
- User explicitly asks to verify or look something up
- High-stakes topics: health, finance, legal

**Do NOT use** for stable knowledge already in context.

### `agent-browser` (replaces `web_open_url`, no API key)

Use `agent-browser` to fetch and read a URL:
```bash
agent-browser fetch "https://...