Foundatio
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
Automate repeated Kagi queries with batch search, watches, notifications, history, caching, and MCP.
Install Kagi Monitoring
$ npx skills add Microck/kagi-cli --skill kagi-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Microck/kagi-cli kagi-monitoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Microck/kagi-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/kagi-monitoring .claude/skills/kagi-monitoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "kagi-monitoring" agent skill from https://github.com/Microck/kagi-cli/tree/main/skills/kagi-monitoring into .claude/skills/kagi-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kagi-monitoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Microck/kagi-cli/tree/main/skills/kagi-monitoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Microck/kagi-cli --skill kagi-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Microck/kagi-cli kagi-monitoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/kagi-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/kagi-monitoring .agents/skills/kagi-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kagi-monitoring" agent skill from https://github.com/Microck/kagi-cli/tree/main/skills/kagi-monitoring into .agents/skills/kagi-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kagi-monitoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Microck/kagi-cli --skill kagi-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Microck/kagi-cli kagi-monitoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/kagi-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/kagi-monitoring .cursor/skills/kagi-monitoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "kagi-monitoring" agent skill from https://github.com/Microck/kagi-cli/tree/main/skills/kagi-monitoring into .cursor/skills/kagi-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kagi-monitoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Microck/kagi-cli.git --path skills/kagi-monitoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Microck/kagi-cli --skill kagi-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Microck/kagi-cli kagi-monitoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/kagi-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/kagi-monitoring .gemini/skills/kagi-monitoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "kagi-monitoring" agent skill from https://github.com/Microck/kagi-cli/tree/main/skills/kagi-monitoring into .gemini/skills/kagi-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kagi-monitoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Microck/kagi-cli kagi-monitoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Microck/kagi-cli --skill kagi-monitoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Microck/kagi-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/kagi-monitoring .github/skills/kagi-monitoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "kagi-monitoring" agent skill from https://github.com/Microck/kagi-cli/tree/main/skills/kagi-monitoring into .github/skills/kagi-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kagi-monitoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Microck/kagi-cli --skill kagi-monitoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Microck/kagi-cli kagi-monitoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Microck/kagi-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/kagi-monitoring .opencode/skills/kagi-monitoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "kagi-monitoring" agent skill from https://github.com/Microck/kagi-cli/tree/main/skills/kagi-monitoring into .opencode/skills/kagi-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kagi-monitoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
kagi-monitoring- GitHub stars
- 180
- Token cost
- ~690 tokens
- SKILL.md length
- 322 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Automate repeated Kagi queries with batch search, watches, notifications, history, caching, and MCP.
- The user needs bulk processing
- SKILL.md covers Choose the workflow, Batch search, Watch search results and Notifications, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Scheduled discovery
What it does
Kagi Monitoring is an agent skill from Microck/kagi-cli. Automate repeated Kagi queries with batch search, watches, notifications, history, caching, and MCP. Use when the user needs bulk processing, scheduled discovery, change detection, or a stable integration surface.
Its SKILL.md is about 690 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Caching and Anomaly detection. It works with Model Context Protocol. The repository describes itself as: terminal CLI for Kagi that gives you command-line access to search, lenses, assistant, summarization, feeds, and paid API commands. The licence is MIT.
When your agent uses it
- The user needs bulk processing
- Scheduled discovery
- Change detection
- A stable integration surface
Example prompts
- “/kagi-monitoring”
Requirements
- Pre-approved tools (allowed-tools): Bash(kagi:*)
What it can do on your machine
Read from SKILL.md and the folder at commit cb64cf5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(kagi:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Kagi Monitoring loads about 690 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 322 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Microck/kagi-cli at commit cb64cf5, republished under its MIT licence (© Microck). 322 words, ~690 tokens.
Download SKILL.mdSave it as
.claude/skills/kagi-monitoring/SKILL.md (or your agent's skills folder).- name
- kagi-monitoring
- description
- Automate repeated Kagi queries with batch search, watches, notifications, history, caching, and MCP. Use when the user needs bulk processing, scheduled discovery, change detection, or a stable integration surface.
- allowed-tools
- Bash(kagi:*)
Kagi Monitoring and Automation
Build repeatable workflows from structured Kagi output. Keep stdout machine-readable and send progress or diagnostics to stderr.
Choose the workflow
| Need | Command |
|---|---|
| Run independent queries together | kagi batch |
| Detect changes in results | kagi watch |
| Deliver a result or alert | kagi notify |
| Inspect prior local activity | kagi history |
| Expose Kagi tools to an agent | kagi mcp |
Run kagi auth status before automating authenticated commands.
Batch search
kagi batch "rust" "zig" "go" --format toon --limit 3
printf 'rust\nzig\ngo\n' | kagi batch --format compactUse argument queries for short fixed sets and stdin for generated lists. Keep the query list as the recoverable input so a failed run can be repeated.
Watch search results
kagi watch "site:example.com release notes" --interval 300Define what counts as a meaningful change before starting a long-running watch. Use a descriptive query and an interval that matches how often the source updates.
Notifications
Use kagi notify --help to select the configured delivery target, then connect
it to a watch or batch result. Never put secrets in notification text or
command history.
History and caching
Use kagi history to inspect local command records before duplicating work.
Use --local-cache only for calls where stale data is acceptable. Never cache
research that must reflect a current price, release, outage, or policy.
MCP
Use the stdio server when another agent host needs Kagi tools:
kagi mcpKeep MCP stdout reserved for protocol messages. Treat a log written to stdout as a protocol-breaking bug.
Automation rules
- Prefer
json,compact, ortoonoverpretty. - Preserve nonzero exit codes instead of turning failure into empty output.
- Keep credentials in Kagi auth storage or environment variables, never scripts.
- Limit concurrency to what the endpoint and account can sustain.
- Record enough input to reproduce a failed item.
- Use a process supervisor or scheduler for long-running watches.
Completion criteria
Automation is complete when:
- inputs and outputs have stable machine-readable shapes;
- failures remain observable and retryable;
- credential values never appear in scripts or logs;
- cache and polling choices match the freshness requirement; and
- long-running processes have a clear owner and stop condition.
© Microck, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/kagi-monitoring of Microck/kagi-cli.
Open the folder on GitHubat commit cb64cf5
Compare with similar skills
Kagi Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Kagi Monitoring this skillMicrock/kagi-cli | 180 | — | ~690 | Automated safety check: Pass | MIT | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Kingdee MCP DevWaHaiLong/KingdeeMCP | 105 | — | ~853 | Automated safety check: Pass | MIT | |
| Dotnet Backend Patternswshobson/agents | 40k | 8 repos | ~6.6k | Automated safety check: Pass | MIT | |
| Frontmcp Configagentfront/frontmcp | 146 | — | ~7k | Automated safety check: Pass | Apache-2.0 | |
| Workosusenotra/notra | 260 | — | ~6.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Kingdee MCP Dev
WaHaiLong/KingdeeMCP
Knowledge base for the Kingdee MCP Dev Squad. An agent skill from WaHaiLong/KingdeeMCP.
Dotnet Backend Patterns
wshobson/agents
Master C/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications.
Frontmcp Config
agentfront/frontmcp
A skill your agent uses when configuring a FrontMCP server through frontmcp.config or the @FrontMcp options.
Workos
usenotra/notra
A skill your agent uses when the user asks for a WorkOS docs URL, term, or dashboard field (Sign-in endpoint, initiateloginuri, Redirect URI, WORKOS env vars), or is implementing, debugging, or…
- Official
Azure Aigateway
microsoft/GitHub-Copilot-for-Azure
Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents.
More from Microck/kagi-cli
Kagi Account Config
Microck/kagi-cli
Configure Kagi CLI credentials, profiles, lenses, custom bangs, redirects, site preferences, and account-backed assistants.
Kagi AI
Microck/kagi-cli
Use Kagi's paid AI allowance for reasoning, coding, research, file analysis, structured generation, or model comparison.
Kagi Assistant
Microck/kagi-cli
Use Kagi Assistant for conversational answers, thread continuity, attachments, streaming, model selection, or custom assistants.
Kagi Usage
Microck/kagi-cli
Search the web, extract or summarize a page, translate it, or check the news with the kagi CLI instead of WebSearch or WebFetch.
Related
Works with
Questions about Kagi Monitoring
What does Kagi Monitoring do?
Automate repeated Kagi queries with batch search, watches, notifications, history, caching, and MCP. Kagi Monitoring is an agent skill from Microck/kagi-cli. Automate repeated Kagi queries with batch search, watches, notifications, history, caching, and MCP.
When should I use Kagi Monitoring?
Kagi Monitoring fits situations like: the user needs bulk processing; scheduled discovery; change detection; A stable integration surface.
How do I install Kagi Monitoring in Claude Code?
Run `npx skills add Microck/kagi-cli --skill kagi-monitoring -a claude-code`. Or copy the skill folder (skills/kagi-monitoring in Microck/kagi-cli) into .claude/skills/kagi-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Kagi Monitoring in Codex?
Run `npx skills add Microck/kagi-cli --skill kagi-monitoring -a codex`. Or copy the skill folder (skills/kagi-monitoring in Microck/kagi-cli) into .agents/skills/kagi-monitoring in your project. Codex loads it when a task matches its description.
Can I use Kagi Monitoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Microck/kagi-cli --skill kagi-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kagi-monitoring, .gemini/skills/kagi-monitoring, .github/skills/kagi-monitoring and .opencode/skills/kagi-monitoring in your project.
What does Kagi Monitoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Kagi Monitoring is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(kagi:*).
Does Kagi Monitoring access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Kagi Monitoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Kagi Monitoring use?
Kagi Monitoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Kagi Monitoring use?
About 690 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Kagi Monitoring?
Skills that share tags, products or a category with Kagi Monitoring: Foundatio (FoundatioFx/Foundatio, 2.1k stars), Kingdee MCP Dev (WaHaiLong/KingdeeMCP, 105 stars), Dotnet Backend Patterns (wshobson/agents, 40k stars) and Frontmcp Config (agentfront/frontmcp, 146 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kagi Monitoring?
Microck (a GitHub user) maintains it in Microck/kagi-cli, which has 180 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.
Source: Microck/kagi-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.