What is generate-tool-permissions?

A documentation tool that builds a complete list of tool permissions from the backend specification. It also updates the related evidence section with the full mapping.

Use it when generating the initial permission mapping, regenerating it after backend changes, or checking that the two documents agree.

It keeps the published permission list consistent with the backend’s tool and endpoint definitions after changes.

How lksnext-ai-lab/spec-kit-template configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to lksnext-ai-lab/spec-kit-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/lksnext-ai-lab/spec-kit-template/main/.github/skills/generate-tool-permissions/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/lksnext-ai-lab/spec-kit-template

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/generate-tool-permissions/github.svg)](https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/generate-tool-permissions)

Your own site

<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/generate-tool-permissions"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/generate-tool-permissions/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/lksnext-ai-lab/spec-kit-template/generate-tool-permissions"><img src="https://agentmods.dev/badge/skills/lksnext-ai-lab/spec-kit-template/generate-tool-permissions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,367 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01367
Opus 5.5	$0.00000	$0.00547
Sonnet 5.5	$0.00000	$0.00273
Haiku 4.5	$0.00000	$0.00137

Measured 2mo ago against content hash 5f31593f1060, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

generate-tool-permissions 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 2mo 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.

.github/skills/generate-tool-permissions/SKILL.md · 134 lines

How it starts

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

Skill: generate-tool-permissions

Propósito

Generar TOOL_PERMISSIONS completo (148 entries) a partir de la tabla de docs/spec/60-backend.md (sección 3) y actualizar EP-001 sección 5 con el mapeo completo.

Este skill es project-specific (no forma parte del framework spec-kit). Mantiene documentación sincronizada con la definición actual del backend.

Cuándo usar

Completar el TODO asociado a la generación de TOOL_PERMISSIONS en evidencia (p.ej. TODO-I03-012)
Regenerar TOOL_PERMISSIONS tras cambios en la tabla de tools de 60-backend.md
Validar consistencia entre la tabla de tools y el mapeo publicado en evidencias

Protocolo de ejecución

1) Leer tabla de tools (60-backend.md sección 3)

Archivo: docs/spec/60-backend.md
Sección: ## 3. Mapeo completo Endpoints HTTP → Tools MCP
Columnas esperadas: | Tool Name | Endpoint HTTP | Permission | Sync/Async | Categoría |
Parsear todas las filas (ignorar header y separador)

2) Extraer entries

Por cada fila de tabla:

Tool Name: columna 1 (snake_case, ej: apps_list, public_chat_call)
Permission: columna 3 (formato resource:operation, ej: apps:read, agents:execute)
Parsear permission: split por : → (resource, operation)

Validaciones mínimas:

Total entries esperado: 148 (si el backend cambia, este número puede cambiar; en ese caso, no inventar: actualizar el “esperado” solo si la tabla fuente lo justifica).
Formato permission: ^[a-z_]+:(read|write|delete|execute)$
No duplicados en tool_name

3) Generar tabla Markdown

Formato output para EP-001 sección 5:

| Tool Name | Resource | Operation |
|-----------|----------|-----------|
| admin_activate_user | admin | write |
| admin_deactivate_user | admin | write |
| ... (entries ordenados alfabéticamente) |
| version_get | version | read |

**Total: 148 tools mapeados**

Orden: alfabético por tool_name.

4) Generar dict Python (opcional, para código middleware)

Read the full file on GitHub · 134 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.

2mo ago First seen · 134 lines · 0 tokens per session scan A 5f31593f1060

Subscribe to this mod's changes

generate-tool-permissions is a skill published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,367 tokens. 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-31.

Security project

generate-tool-permissions next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
generate-tool-permissionslksnext-ai-lab/spec-kit-template	Skill	5	8mo ago	Apache-2.0	A	0	Claude Code, Codex
workspace-managerxuiltul/animaworks	Skill	269	yesterday	Apache-2.0	A	40	Claude Code, Codex
frontmcp-setupagentfront/frontmcp	Skill	148	yesterday	Apache-2.0	A	176	Claude Code, Codex
learn-projectFozikio/cortex-engine	Skill	51	4d ago	MIT	A	21	Claude Code, Codex
project-plannermodimihir07/agentic-os	Skill	217	15d ago	MIT	A	11	Claude Code, Codex
servicenow-hr-ppmKnuckles-Team/servicenow-api	Skill	20	yesterday	MIT	A	133	Claude Code, Codex
initDatus-ai/Datus-agent	Skill	1.9k	yesterday	none	A	103	Claude Code

spec-kit-template: Skill for Claude Code