How do I install the Kagi Account Config skill?

Run npx skillmds@latest add microck/kagi-account-config in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kagi Account Config safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kagi Account Config?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kagi Account Config free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kagi Account Config?

Microck (@microck) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kagi Account Config by microck — Agent Skill

Name: Kagi Account Config
Author: Microck

Kagi Account Config

Configure Kagi CLI credentials, profiles, lenses, custom bangs, redirects, site preferences, and account-backed assistants. Use when the user wants to inspect or change how Kagi authenticates, searches, or applies account settings.

Microck b630328 2.7 KB Updated Sep 17, 2026

File contents

Kagi Account Configuration

Inspect current state before changing it. Never print, echo, or paste stored credential values into output.

Credential model

Credential	Main capabilities
`KAGI_SESSION_TOKEN`	subscriber search, Quick Answer, Assistant, ask-page, translation, subscriber summarization
`KAGI_API_KEY`	current Search API and Extract API
`KAGI_API_TOKEN`	legacy summarize, FastGPT, and Enrichment APIs

Environment variables override .kagi.toml. --profile NAME selects a named profile. Base search prefers session auth when both search credentials are available, unless preferred_auth = "api" is configured.

Inspect and verify auth

kagi auth status
kagi auth check
kagi usage --format pretty

Use status to see credential presence and source. Use check when a configured credential fails at request time.

Use the auth wizard or explicit auth subcommands to set credentials:

kagi auth
kagi auth set --session-token "https://kagi.com/search?token=..."

Never pass secrets on a shared shell command line. Prefer the interactive wizard or protected environment injection in shared environments.

Profiles

Use profiles when separate accounts or credential policies must coexist.

kagi --profile work auth status
kagi --profile personal search "query" --format toon

Verify the selected profile before changing any setting.

Search settings

Inspect before creating, updating, or deleting:

kagi lens list
kagi lens get "Default"
kagi bang custom list
kagi redirect list
kagi site-pref list

Example custom bang:

kagi bang custom create \
  "Docs" \
  --trigger docs \
  --template "https://docs.rs/releases/search?query=%s"

Use each command's --help for the flags a mutation needs. Never delete or overwrite an account setting unless the user asked for it.

Custom assistants

kagi assistant custom list
kagi assistant custom get "Researcher"

Conversation and thread use belongs in kagi-assistant. This skill owns the account-level configuration of custom assistants.

Completion criteria

Configuration work is complete when:

you know the active profile and credential source;
the requested setting is visible through its read command;
no secret value appears in output or persisted scripts;
unrelated account settings remain unchanged; and
you made a destructive change only when the user asked for it.

---name: kagi-account-configdescription: Configure Kagi CLI credentials, profiles, lenses, custom bangs, redirects, site preferences, and account-backed assistants. Use when the user wants to inspect or change how Kagi authenticates, searches, or applies account settings.---# Kagi Account ConfigurationInspect current state before changing it. Never print, echo, or paste storedcredential values into output.## Credential model| Credential | Main capabilities || --- | --- || `KAGI_SESSION_TOKEN` | subscriber search, Quick Answer, Assistant, ask-page, translation, subscriber summarization || `KAGI_API_KEY` | current Search API and Extract API || `KAGI_API_TOKEN` | legacy summarize, FastGPT, and Enrichment APIs |Environment variables override `.kagi.toml`. `--profile NAME` selects a namedprofile. Base search prefers session auth when both search credentials areavailable, unless `preferred_auth = "api"` is configured.## Inspect and verify auth```bashkagi auth statuskagi auth checkkagi usage --format pretty```Use `status` to see credential presence and source. Use `check` when aconfigured credential fails at request time.Use the auth wizard or explicit auth subcommands to set credentials:```bashkagi authkagi auth set --session-token "https://kagi.com/search?token=..."```Never pass secrets on a shared shell command line. Prefer the interactivewizard or protected environment injection in shared environments.## ProfilesUse profiles when separate accounts or credential policies must coexist.```bashkagi --profile work auth statuskagi --profile personal search "query" --format toon```Verify the selected profile before changing any setting.## Search settingsInspect before creating, updating, or deleting:```bashkagi lens listkagi lens get "Default"kagi bang custom listkagi redirect listkagi site-pref list```Example custom bang:```bashkagi bang custom create \ "Docs" \ --trigger docs \ --template "https://docs.rs/releases/search?query=%s"```Use each command's `--help` for the flags a mutation needs. Never delete oroverwrite an account setting unless the user asked for it.## Custom assistants```bashkagi assistant custom listkagi assistant custom get "Researcher"```Conversation and thread use belongs in `kagi-assistant`. This skill owns theaccount-level configuration of custom assistants.## Completion criteriaConfiguration work is complete when:- you know the active profile and credential source;- the requested setting is visible through its read command;- no secret value appears in output or persisted scripts;- unrelated account settings remain unchanged; and- you made a destructive change only when the user asked for it.

Frequently asked questions