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/kumo-ai/kumo-coding-agent/kumo-issuenpx skills add kumo-ai/kumo-coding-agent --skill kumo-issuegit clone --depth 1 https://github.com/kumo-ai/kumo-coding-agentWrote 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/kumo-ai/kumo-coding-agent/kumo-issue)<a href="https://agentmods.dev/skills/kumo-ai/kumo-coding-agent/kumo-issue"><img src="https://agentmods.dev/badge/skills/kumo-ai/kumo-coding-agent/kumo-issue.svg" alt="Measured on agentmods" 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.00076 | $0.00983 |
| Opus 5 | $0.00038 | $0.00491 |
| Sonnet 5 | $0.00015 | $0.00197 |
| Haiku 4.5 | $0.00008 | $0.00098 |
Grade A, and why
kumo-issue 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 6d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File a kumo-coding-agent Issue
Create a structured GitHub issue on kumo-ai/kumo-coding-agent for agent gaps, bugs, or feature requests.
This command works in both Claude Code (interactive) and Codex (headless). In Codex, provide a description as the argument — interactive prompting is not available.
User input: $ARGUMENTS
Instructions
Step 1: Validate GitHub CLI Auth
Run:
gh auth status
If gh is not authenticated, tell the user to run gh auth login -h github.com
first and stop before gathering more information.
Step 2: Gather Information
If $ARGUMENTS is provided, parse it to understand the issue.
If $ARGUMENTS is empty, ask the user these questions (skip in headless mode):
- What happened? (What were you trying to do?)
- Which skill or context doc was involved? (If known)
- What did you expect vs what happened?
Step 3: Classify the Issue
Determine the type based on the description:
| Type | Signal | Label |
|---|---|---|
| gap | "agent didn't know", "missing info", "couldn't answer" | gap |
| bug | "wrong info", "incorrect", "outdated", "says X but should be Y" | bug |
| feature | "add support for", "new skill", "new vertical", "would be nice" | enhancement |
Step 4: Identify Affected Files
Search for files related to the issue:
grep -rl "<relevant keyword>" context/ skills/
If the user mentioned a specific file, verify it exists and note the relevant section.
Also check if this is already tracked:
grep -i "<keyword>" context/_gaps.yaml
If already tracked, tell the user and ask if they still want to file an issue.
Step 5: Compose the Issue
Title format: kumo: <concise description>
Examples:
kumo: missing Databricks Unity Catalog connector docskumo: pql-syntax.md lists MODE as valid aggregationkumo: add healthcare/clinical trials vertical
Body template:
## Type
<gap | bug | feature>
## Affected File(s)
- `<path>` (line ~N)
## Description
<Clear description of the issue>
## Expected Behavior
<What should happen / what info should be there>
## Current Behavior
<What actually happens / what the doc currently says>
## Suggested Fix
<If obvious — otherwise "Needs investigation">
## Context
<Any additional context: SDK version, customer use case, etc.>
---
*Filed via `/kumo-issue` by @REPORTER*
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.
- 6d ago First seen · 143 lines · 76 tokens per session scan A 8c97c040e2e9
kumo-issue is a skill published in the GitHub repository kumo-ai/kumo-coding-agent (39 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 983 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-30.
Other skills, from other repositories
general
Handle everyday conversation, answer questions, manage files, take notes, run scripts, and maintain persistent memory across sessions. Use when the user asks a general question, requests file operations, wants to brainstorm ideas, needs to-do tracking, asks you to remember something, or requests skill search and…
multi-bot
Coordinates responses between multiple GolemBot instances in a shared fleet. Use when the bot operates in a group chat with other bots, needs to decide whether to respond or pass, or must call a peer bot's API to fetch cross-domain data.
kb-guide
Search, read, create, and update knowledge base entries via MCP-connected KB tools. Use when the user asks to look up documentation, find existing articles, check if docs exist on a topic, create a new KB entry, update an existing document, or when domain questions should be answered from the knowledge base first.
ops
Content operations assistant — drafts blog posts, social media copy, and marketing materials, compiles data briefings, and tracks competitor activity. Use when the user asks to write a blog post, draft social media content, create marketing copy, generate a weekly report, compile operational metrics, update the…
escalation
Escalate unresolvable or sensitive requests to a human agent by recording an escalation entry. Use when the user asks to speak to a human, the bot cannot answer confidently, the request involves financial, legal, or security concerns, a safety issue is detected, or the user is frustrated after repeated failures.
code-review
Reviews code changes, pull requests, and diffs for correctness, security, performance, and style. Use when the user submits a PR for review, asks to review a diff or code snippet, or requests a quality check on recent changes.