approve

approve is a skill for Claude Code from idosreisjunior/sdd-claude-kit. It costs 94 tokens per session (1,355 once invoked), scanned A, original, Apache-2.0.

Uma etapa que registra a aprovação humana de um plano e muda seu estado de PLANNED para APPROVED. Ela guarda quem aprovou, quando aprovou e a versão exata da especificação aprovada.

In plain words
What is it for?
Serve para confirmar formalmente um plano antes da implementação, registrar o responsável e garantir que o código será feito a partir da versão aprovada da especificação.
Why use it?
Evita que o sistema trate uma decisão do modelo como autorização humana. Se a especificação for editada depois, a aprovação deixa de ser válida.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the NotebookEdit tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the sdd-kit plugin — 9 skills shipped together

Good fit Serve para confirmar formalmente um plano antes da implementação, registrar o responsável e garantir que o código será feito a partir da versão aprovada da especificação.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add idosreisjunior/sdd-claude-kit
Claude Code
/plugin install sdd-kit

Made for: Claude Code.

Or install sdd-kit, the plugin that ships this one along with the rest of its 9 skills.

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.

agentmods badge for approve

README.md
[![agentmods](https://agentmods.dev/badge/skills/idosreisjunior/sdd-claude-kit/approve/github.svg)](https://agentmods.dev/skills/idosreisjunior/sdd-claude-kit/approve)
Your own site
<a href="https://agentmods.dev/skills/idosreisjunior/sdd-claude-kit/approve"><img src="https://agentmods.dev/badge/skills/idosreisjunior/sdd-claude-kit/approve/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.

agentmods 80×15 button for approve

Your own site · 80×15
<a href="https://agentmods.dev/skills/idosreisjunior/sdd-claude-kit/approve"><img src="https://agentmods.dev/badge/skills/idosreisjunior/sdd-claude-kit/approve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,355 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00094 $0.01355
Opus 5 $0.00047 $0.00678
Sonnet 5 $0.00019 $0.00271
Haiku 4.5 $0.00009 $0.00136

Measured 10d ago against content hash 6d9c2f9e9df9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

approve 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 10d 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.

plugins/sdd-kit/skills/approve/SKILL.md · 94 lines

How it starts

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

/sdd-kit:approve — registrar a aprovação humana

Registra a aprovação de um plano e promove a mudança para APPROVED — o estado do qual /sdd-kit:implement parte.

Por que esta skill NÃO é autoinvocável

disable-model-invocation: true não é um detalhe de configuração — é a garantia do Artigo 3. Esta skill registra uma decisão humana. Se o modelo pudesse invocá-la sozinho, poderia gravar approval.by sem que ninguém tivesse aprovado, e o Artigo 3 viraria encenação com rastro documental. A skill só age quando o usuário a invoca e aprova explicitamente. Ver ADR-008 e ADR-011. Se alguém editar este front matter no futuro, esta seção diz por que o campo estava aqui.

Modo de governança

Leia workflow.mode de .specs/config.yaml antes de agir.

Modo Comportamento desta skill
advisory Informa o estado e o que a aprovação registraria; nunca bloqueia — mas também nunca grava sem o ato humano
guided (padrão) Exige a frase de aprovação explícita do usuário antes de gravar
strict Ainda não implementado na Fase 1. Informe isso ao usuário e opere como guided

Nunca finja um bloqueio que não existe. Dizer que o modo strict impediu algo, quando ele não está implementado, é pior que não ter o modo — cria confiança em uma proteção ausente.

Arquivos que esta skill lê

Quando O quê
Sempre .specs/config.yaml — idioma e modo
Sempre <dir-da-mudança>/spec.md — para calcular a revisão aprovada (o hash)
Sempre <dir-da-mudança>/status.yaml — estado atual e o campo approval
Se existir <dir-da-mudança>/tasks.md e traceability.yaml — para o usuário revisar o plano aprovado

Procedimento

1. Verificar a pré-condição de estado

O argumento é o identificador. Leia status.yaml. A promoção a APPROVED só é válida a partir de PLANNED (grafo em ${CLAUDE_PLUGIN_ROOT}/schemas/workflow.json). Se o estado for outro, recuse com origem, destino e as transições válidas a partir da origem, sem alterar status nem history (SCN-SWC-007):

Read the full file on GitHub · 94 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. 10d ago First seen · 94 lines · 94 tokens per session scan A 6d9c2f9e9df9

Subscribe to this mod's changes

approve is a skill published in the GitHub repository idosreisjunior/sdd-claude-kit (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,355 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.

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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens