agentmods.dev

capabilities-manage

A Kode guide for managing configurable features such as language support, status displays, output styles, plugins, and notifications.

In plain words
What is it for?
Use it when enabling, disabling, or configuring a Kode capability, or when checking why one is not working.
Why use it?
It provides a structured way to diagnose and change these settings while keeping changes minimal and reversible.

Skill for Claude CodeCodex

5.2k +2 6d ago A scan 90 tokens original Apache-2.0
View the source file shareAI-lab/Kode-CLI
Install

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.

agentmods
npx agentmods add skills/shareai-lab/kode-cli/capabilities-manage
Any agent
npx skills add shareAI-lab/Kode-CLI --skill capabilities-manage
Clone the repo
git clone --depth 1 https://github.com/shareAI-lab/Kode-CLI

Made for: Claude Code, Codex.

Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 706 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00090 $0.00706
Opus 5 $0.00045 $0.00353
Sonnet 5 $0.00018 $0.00141
Haiku 4.5 $0.00009 $0.00071

Measured 3d ago against content hash 0c792f9d2c0d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

capabilities-manage 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 3d 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.

packages/builtin-skills/skills/capabilities-manage/SKILL.md · 48 lines

How it starts

The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Capabilities Manage

Goal

Make users manage Kode features by expressing intent (“enable LSP for TS”, “fix my statusline”) while the agent performs the necessary actions via the agent CLI.

Rules (do not violate)

  • Do not output “installation menu” scripts or long lists of install commands.
  • Prefer SlashCommand to run Kode commands (/statusline, /lsp, /plugin ...) instead of asking the user to do it manually.
  • Keep changes minimal and reversible; verify after each change.

Workflow

  1. Clarify which capability: statusline / lsp / output-style / plugins (or multiple).
  2. Inspect current state with minimal friction:
    • Read settings files (~/.kode/settings.json, .kode/settings.local.json).
    • For interactive status screens, ask the user to open them (single step): /lsp, /output-style.
  3. Apply changes:
    • statusline: create a Task with subagent_type statusline-setup (do not ask the user to memorize the command).
    • lsp: ensure a plugin provides .lsp.json mappings; manage via /plugin, then re-check via /lsp screen.
    • output styles: set outputStyle in settings (or ask the user to choose via /output-style); for edits, edit the output style markdown file and then re-check /output-style.
  4. Verify: re-check status screens and run a minimal real operation.

Keep this fast and low-friction: default output should be a short checklist and only one question when a choice is required.

  1. Read current settings (best effort):
    • ~/.kode/settings.json (global)
    • .kode/settings.local.json (project, if present)
  2. Produce a compact checklist (OK / Needs attention) for:
    • Statusline: global settings.json contains statusLine.
    • Output style: either settings file contains a non-empty outputStyle string.
    • Plugins & LSP readiness: mention that LSP is plugin-driven; if the user cares, ask them to open /lsp (single step) to confirm resolved servers.
    • Permission friction: if the user reports unexpected denials/repeated prompts, invoke the permissions-debug skill.
  3. Auto-fix what you can safely:
    • Statusline: if requested, create a Task with subagent_type statusline-setup (do not ask the user to memorize the command).
    • Output style: set outputStyle in .kode/settings.local.json (project) or ~/.kode/settings.json (global) and re-read to verify.
  4. Verify each fix immediately by re-reading the changed file(s) and summarizing what changed.

Read the full file on GitHub · 48 lines

Changes

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.

  1. 3d ago First seen · 48 lines · 90 tokens per session scan A 0c792f9d2c0d

Subscribe to this mod's changes

capabilities-manage is a skill published in the GitHub repository shareAI-lab/Kode-CLI (5,212 stars, last pushed 6d ago), licensed Apache-2.0. It adds 90 tokens to every session and 706 once invoked, about $0.0005 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.

Building agents
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens