Bernstein Approve

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkDeclared6 observations
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

API="${BERNSTEIN_API_URL:-http://127.0.0.1:8052}"

Audit 0.4.1 · source sha 6ba64a7d2489 · 14 Oct 2026Report an issue or request a re-scan

• Publishersipyourdrink-ltd GitHub organizationOwner of the repository this skill is read from
• Source foldersipyourdrink-ltd/bernstein/packages/cursor-plugin/skills/bernstein-approveThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict6ba64a7d2489A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.

---
name: bernstein-approve
description: >
  Review and approve/reject pending tasks or plans in Bernstein.
  Use when the user asks about approvals, wants to review agent work,
  or needs to approve/reject a plan before execution begins.
---

# Bernstein Approvals

Review pending approvals and plans, then approve or reject them.

## When to Use

- User asks "any pending approvals?" or "what needs my review?"
- User wants to approve or reject a completed task
- User wants to review and approve/reject a plan before agents execute it
- User says "approve that" or "reject task X"

## Instructions

### List pending approvals

1. Run `scripts/approvals.sh list` to fetch pending approvals and plans.
2. Present each item with its diff summary and test results:

```
## Pending Approvals

### Task TASK-042: Fix auth middleware
**Agent:** claude-backend-01 | **Role:** backend
**Files changed:** src/auth/middleware.py (+42 -8)
**Tests:** 14/14 passing

[Approve] [Reject]
```

### Approve or reject

3. When the user decides:
   - Approve: `scripts/approvals.sh approve <task_id> "reason"`
   - Reject: `scripts/approvals.sh reject <task_id> "reason"`

4. For **plans** (multi-task proposals):
   - List plans: `scripts/approvals.sh plans`
   - Approve plan: `scripts/approvals.sh approve-plan <plan_id>`
   - Reject plan: `scripts/approvals.sh reject-plan <plan_id>`

### After approval

5. Confirm the action and note what happens next:
   - Approved tasks → agent commits and merges
   - Approved plans → planned tasks promoted to open, agents start picking them up
   - Rejected → task goes back to open for retry, or gets cancelled

Excerpt, first 1,639 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/sipyourdrink-ltd/bernstein
git -C bernstein checkout 6ba64a7d2489

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 6ba64a7d2489

Questions about Bernstein Approve

• github.com/sipyourdrink-ltd/bernstein/tree/main/packages/cursor- — the audited source at commit 6ba64a7d2489 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology