Borrowing it
Nothing to install: this file belongs to kumo-ai/kumo-coding-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kumo-ai/kumo-coding-agent/main/.claude/skills/kumo-pr/SKILL.mdgit 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-pr)<a href="https://agentmods.dev/skills/kumo-ai/kumo-coding-agent/kumo-pr"><img src="https://agentmods.dev/badge/skills/kumo-ai/kumo-coding-agent/kumo-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kumo-ai/kumo-coding-agent/kumo-pr"><img src="https://agentmods.dev/badge/skills/kumo-ai/kumo-coding-agent/kumo-pr.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.01242 |
| Opus 5.5 | $0.00030 | $0.00497 |
| Sonnet 5.5 | $0.00015 | $0.00248 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade C, and why
kumo-pr scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "$WORK_DIR" How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix kumo-coding-agent and Open a PR
Create a branch, apply fixes to kumo-coding-agent skills or context docs, and open a pull request for review.
This command works in both Claude Code (interactive) and Codex (headless). In Codex, provide a description of the fix 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 creating a branch or making changes.
Step 2: Understand the Fix
If $ARGUMENTS is provided, parse it to understand what needs to change.
If $ARGUMENTS is empty, ask the user (skip in headless mode):
- Which file needs fixing? (skill, context doc, or vertical)
- What's wrong with it?
- Do you know the correct information?
Step 3: Detect Environment and Create a Branch
Generate <slug> from the fix description: lowercase, hyphens, max 50 chars.
Examples: fix-pql-time-units, add-databricks-connector-docs, update-fraud-vertical.
Check whether we're already inside the kumo-coding-agent repo:
git remote get-url origin 2>/dev/null | grep -q "kumo-coding-agent"
If YES (already in the right repo):
git checkout main
git pull --ff-only origin main 2>/dev/null || true
git checkout -b kumo-coding-agent/<slug>
# WORK_DIR = current directory
If NO (e.g., running from a project that installed the skills via npx skills add):
WORK_DIR=$(mktemp -d)
git clone --filter=blob:none --depth=1 \
[email protected]:kumo-ai/kumo-coding-agent.git "$WORK_DIR"
cd "$WORK_DIR"
git checkout -b kumo-coding-agent/<slug>
All subsequent steps operate inside $WORK_DIR. Remember it for cleanup.
Step 4: Make the Changes
Apply the requested fixes.
Guidelines:
- Follow existing document structure and conventions
- If updating a context doc, update the Source header date
- If adding new content, keep the same style as surrounding content
- If fixing a claim, check the authoritative source (see
meta/skills/verify-content.mdfor source locations)
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.
- 1mo ago First seen · 172 lines · 74 tokens per session scan C f1e20ac24a4a
kumo-pr is a skill published in the GitHub repository kumo-ai/kumo-coding-agent (39 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 1,242 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
release-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.
audit-release
A pre-release review assistant that checks whether a software package or plugin is ready to publish.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.