aistack-consensus

aistack-consensus is a skill for Claude Code from blackms/aistack. It costs 75 tokens per session (627 once invoked), scanned A, original, MIT.

A human-approval checkpoint system for aistack agents. It lets an agent propose an action and pause until an authorised person approves or rejects it.

In plain words
What is it for?
Use it to create pending approvals, list or inspect them, and approve or reject proposed high-impact actions before they run.
Why use it?
It prevents unattended agents from carrying out risky or hard-to-reverse actions such as production deployments, database changes, mass edits or data deletion.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the aistack plugin — 3 skills, 3 commands shipped together

Good fit Use it to create pending approvals, list or inspect them, and approve or reject proposed high-impact actions before they run.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/blackms/aistack/consensus
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 blackms/aistack --skill consensus
Clone the repo
git clone --depth 1 https://github.com/blackms/aistack

Made for: Claude Code.

Or install aistack, the plugin that ships this one along with the rest of its 3 skills, 3 commands.

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 aistack-consensus

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/blackms/aistack/consensus"><img src="https://agentmods.dev/badge/skills/blackms/aistack/consensus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 627 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.00075 $0.00627
Opus 5.5 $0.00030 $0.00251
Sonnet 5.5 $0.00015 $0.00125
Haiku 4.5 $0.00007 $0.00063

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

Security

Grade A, and why

aistack-consensus 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.

plugin/skills/consensus/SKILL.md · 45 lines

How it starts

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

aistack: Consensus checkpoints (human-in-the-loop)

aistack lets agents pause before high-impact actions and request explicit approval. This prevents autonomous agents from taking irreversible or risky steps without a human (or a designated approver) signing off.

When to use

  • Before an irreversible or high-blast-radius action: production deploy, DB schema migration, deleting data, force-push, mass file rewrite, spending money, sending external messages.
  • When the user wants approval gates, sign-off, or "ask me before doing X".
  • In an autonomous loop (see /aistack-pm) where some steps must not run unattended.

For low-risk, easily reversible actions, do NOT add a checkpoint — it just adds friction.

MCP tools (bundled aistack server)

Tool Purpose
consensus_check Propose an action and create a pending checkpoint requiring approval
consensus_list_pending List checkpoints awaiting a decision
consensus_get Inspect a specific checkpoint
consensus_approve Approve a pending checkpoint (the action may proceed)
consensus_reject Reject a checkpoint (the action must not proceed)

List exact schemas with npx @blackms/aistack mcp tools.

Workflow

  1. Detect the gate: classify the next action's risk. If it is irreversible / high-impact, do not execute it directly.
  2. Propose: call consensus_check describing the exact action, its blast radius, and how to undo it (if possible). This creates a pending checkpoint.
  3. Pause & surface: stop and tell the human what is pending and why, then wait. Do not proceed on assumption.
  4. Resolve: on consensus_approve, perform the action. On consensus_reject, abort cleanly, report, and propose a safer alternative if one exists.
  5. Record: store the decision and its rationale in aistack memory (see the aistack-memory skill) for an audit trail.

Tips

  • Make each proposal self-contained: a reviewer should be able to decide from the checkpoint text alone, without re-reading the whole session.
  • Default to a checkpoint when uncertain whether an action is reversible. Over-gating is annoying; under-gating is dangerous.
  • Combine with /aistack-review to run an adversarial pass before requesting approval, so the human reviews a vetted action.

Read the full file on GitHub · 45 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. 2mo ago First seen · 45 lines · 75 tokens per session scan A 85533b20cdc1

Subscribe to this mod's changes

aistack-consensus is a skill published in the GitHub repository blackms/aistack (53 stars, last pushed 5mo ago), licensed MIT. It adds 75 tokens to every session and 627 once invoked, about $0.0003 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-08-30.

Related

aistack-consensus compared with skills from other repositories

aistack-consensus next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
aistack-consensusblackms/aistackSkill535mo agoMITA75Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code