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/kleaphq/cli/skillnpx skills add kleaphq/cli --skill skillgit clone --depth 1 https://github.com/kleaphq/cliWhat 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.00088 | $0.00801 |
| Opus 5 | $0.00044 | $0.00400 |
| Sonnet 5 | $0.00018 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
kleap 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Driving Kleap
Kleap is website infrastructure for agents: you describe a site, Kleap builds it
(hosting + database + auth included), connects a domain, and publishes it with a
verified-live guarantee. You drive it through the Kleap MCP tools
(create_app, modify_app, check_task, publish_app, etc.).
The golden rule: never claim a site is live until Kleap confirms it
A deploy being started is NOT the same as a site being online. Only state
that a site is live after get_publish_status (or check_task) returns
status: "published" with a production_url. If it isn't confirmed, say so
plainly — never invent a working URL.
Core flow — create a site
create_app({ prompt })— give a detailed description. Returns{ app_id, task_id }.- Poll
check_task({ task_id })every ~10–15s untilstatusiscompletedorfailed. Building usually takes a couple of minutes (up to ~15 for complex sites) — check_task long-polls so you don't babysit it. - If
failed(transient stalls happen): callretry_task({ task_id })with the SAME task_id — it resumes from partial state and preserves files already written. Do not start a brand-newcreate_app. Then pollcheck_taskon the new task_id. Retry once or twice before giving up. publish_app({ app_id })→ then pollget_publish_status({ app_id })untilstatus: "published". Report theproduction_urlonly then.
Edit an existing site
modify_app({ app_id, message }) with a clear, specific instruction (e.g.
"Change the headline to X and make the background charcoal"). It returns a task —
poll check_task, then publish_app to push the change live. Editing is
reliable; prefer it over recreating.
Domains
search_domains({ query })— find available names. You cannot buy a domain — purchase is confirmed by the user in Kleap. Tell the user to complete the purchase there, then continue.connect_domain({ app_id, domain })— connect a domain the user ALREADY owns to a published app (the app must be published first). The user points the domain's A record to Kleap; TLS is automatic.check_domain({ domain })— DNS / connection status.
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 · 65 lines · 88 tokens per session scan A c55e5be0951c
kleap is a skill published in the GitHub repository kleaphq/cli (1 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 801 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-08-31.
Other skills, from other repositories
9router-video
Generate videos via 9Router /v1/videos/generations using xAI Grok Imagine (grok-imagine-video). Async job flow - submit, poll requestid until done, download MP4. Use when the user wants to create, generate, or render a video, text-to-video (txt2vid), or image-to-video.
9router-web-search
Web and X search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / You.com / Perplexity / Xquik. Use when the user wants to search the web, find articles, or search public X posts.
9router-stt
Speech-to-text via 9Router /v1/audio/transcriptions using OpenAI Whisper / Groq / Gemini / Deepgram / AssemblyAI / NVIDIA / HuggingFace models. Use when the user wants to transcribe audio, convert speech to text, or get subtitles from audio files.
9router-tts
Text-to-speech via 9Router /v1/audio/speech using OpenAI / ElevenLabs / Deepgram / Edge TTS / Google TTS / Hyperbolic / Inworld voices. Use when the user wants to convert text to speech, generate audio, voiceover, narrate, or read text aloud.
9router-web-fetch
Fetch URL → markdown / text / HTML via 9Router /v1/web/fetch using Firecrawl / Jina Reader / Tavily Extract / Exa Contents. Use when the user wants to scrape a webpage, extract URL content, read article, or convert a URL to markdown.
9router
Entry point for 9Router — local/remote AI gateway with OpenAI-compatible REST for chat, image, TTS, embeddings, web search, web fetch. Use when the user mentions 9Router, NINEROUTERURL, or wants AI without writing provider boilerplate. This skill covers setup + indexes capability skills; fetch the relevant capability…