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/shareai-lab/kode-cli/permissions-debugnpx skills add shareAI-lab/Kode-CLI --skill permissions-debuggit clone --depth 1 https://github.com/shareAI-lab/Kode-CLIWhat 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 | $0.00053 | $0.00437 |
| Opus 5 | $0.00026 | $0.00218 |
| Sonnet 5 | $0.00011 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
permissions-debug 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 2d 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.
What it actually says
Permissions Debug (Kode-first, fail-closed)
Non-negotiables
- Do not auto-escalate permissions. If an action would normally require user approval, keep it interactive and explain why.
- Prefer minimal, reversible permission changes and verify immediately.
- In
dontAskcontexts, treat “would prompt” as deny (fail-closed). Do not try to bypass.
Fast triage (what to check first)
-
Confirm what is blocked
- Look for the exact tool name and the rejection message.
- If the failure is from a subagent, confirm whether the parent context was more restricted.
-
Inspect approved tools / project allowlist
- Use
SlashCommandto run/approved-tools listand confirm whether the tool (or its rule category) is present. - If the list is unexpectedly long or contains stale entries, remove only the minimum needed with
/approved-tools remove <tool>.
- Use
-
Check per-command constraints
- Some flows apply
commandAllowedToolsconstraints (slash command / skill execution contexts). Confirm the command’sallowed-toolsfrontmatter and whether it should be restrictive.
- Some flows apply
Verification loop (keep it tight)
- Re-run the exact action that was blocked and confirm:
- whether the prompt appears (interactive modes), or
- whether the tool is allowed/denied deterministically (headless /
dontAsk).
Forensics (when “it should have worked”)
- Inspect the latest session artifacts under
~/.kode/(messages + errors) to confirm what tool call was attempted and why it was denied. - If a background shell was involved, cross-check task output files in
~/.kode/**/tasks/for the correspondingbashId.
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.
- 2d ago First seen · 38 lines · 53 tokens per session scan A b42c9d3dfc6b
permissions-debug is a skill published in the GitHub repository shareAI-lab/Kode-CLI (5,212 stars, last pushed 5d ago), licensed Apache-2.0. It adds 53 tokens to every session and 437 once invoked, about $0.0003 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
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.