neuron-tool-approval

neuron-tool-approval is a skill for Claude Code, Codex from neuron-core/neuron-laravel. It costs 103 tokens per session (3,862 once invoked), scanned A, original, MIT.

A human-approval workflow for Neuron AI tools. The agent pauses before a configured tool runs, shows the request in the chat interface, and continues after someone approves or rejects it.

In plain words
What is it for?
Use it to add approval gates to tools, display pending decisions, process approve or deny responses, and handle both normal chat turns and approval continuations.
Why use it?
It prevents risky or consequential tool actions from happening without a person's decision. It also provides the server and interface flow needed to resume the paused conversation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add approval gates to tools, display pending decisions, process approve or deny responses, and handle both normal chat turns and approval continuations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/neuron-core/neuron-laravel/neuron-tool-approval
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.

Any agent
npx skills add neuron-core/neuron-laravel --skill neuron-tool-approval
Clone the repo
git clone --depth 1 https://github.com/neuron-core/neuron-laravel

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.

agentmods badge for neuron-tool-approval

README.md
[![agentmods](https://agentmods.dev/badge/skills/neuron-core/neuron-laravel/neuron-tool-approval/github.svg)](https://agentmods.dev/skills/neuron-core/neuron-laravel/neuron-tool-approval)
Your own site
<a href="https://agentmods.dev/skills/neuron-core/neuron-laravel/neuron-tool-approval"><img src="https://agentmods.dev/badge/skills/neuron-core/neuron-laravel/neuron-tool-approval/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 neuron-tool-approval

Your own site · 80×15
<a href="https://agentmods.dev/skills/neuron-core/neuron-laravel/neuron-tool-approval"><img src="https://agentmods.dev/badge/skills/neuron-core/neuron-laravel/neuron-tool-approval.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,862 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.00103 $0.03862
Opus 5.5 $0.00041 $0.01545
Sonnet 5.5 $0.00021 $0.00772
Haiku 4.5 $0.00010 $0.00386

Measured 15d ago against content hash 438469b50b81, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

neuron-tool-approval 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 15d 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.

resources/boost/skills/neuron-tool-approval/SKILL.md · 278 lines

How it starts

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

Neuron AI Tool Approval

This skill helps you gate agent tool execution behind human approval and build the application around it: the server endpoint, the UI, and the decision round trip.

Use Agent::submitApprovalDecisions($decisions) for tool approval and Agent::submitToolResults($results) for deferred tool results. Both accept maps keyed by tool call ID and stage a continuation; finish with run() for an AgentState or events() for a stream.

The Mental Model

Approval is owned by ToolNode and configured on the tools themselves. There is no middleware to attach: each tool declares whether it needs approval, you override that per instance when you attach it to the agent, and the node suspends the run before executing anything undecided.

Chat history is what the application reads; the thread is the workflow ID. Which tools await a decision and why each one is asking live on the last message of the thread, written once at suspend time — you never inspect workflow state and never boot the agent just to render. Continuing needs no runId either: the run's durable records live in the partition named by the threadId itself, so the approve endpoint rebuilds the agent from the thread ID alone, stages the decisions with submitApprovalDecisions($decisions), and finishes with run() or events(). No workflow coordination ID is stored on the side.

Two facts shape the UI:

  • History is append-only. The suspended tool_call message keeps its pending snapshot forever; the final outcomes (approved/rejected + feedback + results) are recorded on the tool_call_result message that follows it. "Is approval pending?" = the thread tail is a tool_call with pending tools.
  • Partial decisions are retained by ToolNode through durable memos. Each submission can contain only the newest decisions, through submitApprovalDecisions($decisions). Explicit updates to an already-decided action in a still-open batch win.

Enabling Approval

Two requirements for cross-process flows: workflow persistence (the suspension/continuation machinery) and a durable chat history (the record itself — InMemoryChatHistory keeps the safety property but loses the thread across processes).

Read the full file on GitHub · 278 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. 15d ago First seen · 278 lines · 103 tokens per session scan A 438469b50b81

Subscribe to this mod's changes

neuron-tool-approval is a skill published in the GitHub repository neuron-core/neuron-laravel (122 stars, last pushed 16d ago), licensed MIT. It adds 103 tokens to every session and 3,862 once invoked, about $0.0004 per session on Opus 5.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-10-01.