Bernstein Agents

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkUndeclared4 observations, not in its own description
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

DASH_JSON="$(curl -sf "${HEADERS[@]}" "$API/dashboard/data" 2>/dev/null || true)"

curl -sf "${HEADERS[@]}" "$API/agents/$ID/logs?tail_bytes=4096" || echo '{"error": "Could not fetch logs"}' >&2

curl -sf "${HEADERS[@]}" -X POST "$API/agents/$ID/kill" || echo '{"error": "Could not kill agent"}' >&2

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

network use found in code, not declared in the description

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-agentsThe 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: Manage Bernstein agents - list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one.

---
name: bernstein-agents
description: >
  Manage Bernstein agents - list active agents, inspect their output,
  kill stalled agents, or stream live logs. Use when the user asks about
  agents, wants to see what an agent is doing, or needs to kill one.
---

# Bernstein Agent Management

Inspect, monitor, and control active Bernstein agents.

## When to Use

- User asks "what agents are running?" or "show me the agents"
- User wants to see what a specific agent is working on
- User says "kill that agent" or "stop the backend agent"
- User asks "why is that agent stuck?" or wants to inspect agent output
- User wants to see agent logs

## Instructions

### List agents

1. Run `scripts/agents.sh list` to get all active agents.
2. Present them clearly:

```
## Active Agents (3)

| Agent | Role | Model | Status | Task | Runtime | Cost |
|-------|------|-------|--------|------|---------|------|
| ses-a1b2 | backend | claude-sonnet-4 | alive | TASK-042: Fix auth | 4m 12s | $0.32 |
| ses-c3d4 | qa | gpt-4.1 | alive | TASK-043: Write tests | 2m 45s | $0.18 |
| ses-e5f6 | frontend | claude-sonnet-4 | stalled | TASK-044: Update UI | 8m 03s | $0.51 |
```

### Inspect agent

3. To see what an agent is doing: `scripts/agents.sh logs <session_id>`
4. Show the last ~20 lines of output.

### Kill agent

5. To kill a stalled or misbehaving agent: `scripts/agents.sh kill <session_id>`
6. Confirm: "Agent ses-e5f6 terminated. Task TASK-044 returned to open queue."

### Stall detection

7. If any agent shows `stalled` status, proactively suggest killing it.
8. An agent is stalled if it hasn't sent a heartbeat in >60 seconds.

Excerpt, first 1,630 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
   !CAUTION B 89 / 100

   first audit · source 6ba64a7d2489

Questions about Bernstein Agents

• 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