Atlas / Skills / benjaminstelzer / scoville-suite-for-codex

scoville-suite-for-codexBLOCK

skills/benjaminstelzer/scoville-suite-for-codex

Native Codex workflow, planning, code, UI, handoff, advisers and project configuration.

Verdict
BLOCK
Grade
D
Trust score
69 /100
Version
—
Hosts
3 documented
License
—
Stars
0
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Scoville helps Codex plan, implement and review work that spans more than one conversation. Workflow runs the work step by step in the Plan's order, Ask brings in independent advice, and Handoff carries unfinished tasks into the next session. Setup manages the project's model and Workflow settings.

Scoville is the scale for chili heat. These Skills aim for sharper work and less diluted context. Adding more instructions is easy. Keeping the useful ones is the point.

Using Claude Code or another Agent Skills host? Take Scoville Suite. On Codex desktop, take Scoville Suite for Codex, which adds Workflow, Ask and Setup.

Scoville Workflow for Codex

Scoville Workflow takes a prepared Plan through implementation, independent review and corrections. A manager assigns bounded work, executors implement it and reviewers check the result. Progress stays in the Plan across sessions.

Use Plan and Ask to settle requirements and acceptance first, then

Read from source at commit 218c0b65fb28OBSERVED · 2026-10-10
Advertisement
02

Install

Commands as the repository documents them. They are shown, not run.

uv tool run --from 'git+https://github.com/agentskills/agentskills.git@69ef37e9424c0a7ea9dd2293b559e43ec8176379#subdirector
03

Host compatibility

What the documentation claims. We have not run a compatibility test.

HostStatusNotes
claude-codementioned
codexmentioned
cursormentioned
04

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: scoville-ask-for-codex
description: Ask one or more configured advisers for independent advice or reviews from Codex, through fresh Codex subagents or Claude CLI. Use when the user requests an Ask consultation, a second opinion, or a review by specified advisers. Ordinary questions to the current assistant do not trigger a consultation.
compatibility: "Codex desktop online, Python 3.11+ and filesystem access. Native advisers require collaboration agent tools. Claude advisers require authenticated Claude Code CLI; Opus 5.5 requires CLI 2.1.280+."
---

# Scoville Ask for Codex

Collect independent answers in the calling task. A review asks each adviser to
assess the same evidence; a general consultation combines independent answers
into a synthesis. The caller owns any subsequent changes. Advisers keep the reviewed subject unchanged and never delegate the consultation.

When writing adviser framing or reporting results, read and apply the
[shared writing rules](references/writing.md). The helpers include those rules
for adviser answers while preserving the literal user question.

## Choose the consultation

Infer `review` or `consultation` from the actual question; an explicit mode wins.
“Could this patch lose data?” is a review even without “for review”. If the
intended outcome is ambiguous, clarify before dispatch. Do not ask again when
the request already establishes the mode, advisers or permission.

Resolve settings with `scripts/ask.py`:

| Priority | Settings source |
| --- | --- |
| 1 | Unsaved request overrides. |
| 2 | Selected project's `.scoville/config.json`, `ask` section. |
| 3 | [config.default.json](config.default.json). |

| Adviser selection | Presets |
| --- | --- |
| Explicitly named | Exactly those presets, even if absent from the default list. |
| None named | Default adviser list; it is not an allowlist. |

Select exactly the requested routes, models and efforts. Adviser IDs identify
results; display names are not agent handles. Resolve selected presets in one
call and report each adviser's settings. Read
[configuration and helper inputs](references/configuration.md) for resolution,
migration or the first helper invocation.

{{ include: rules.python }}

Native spawn_agent validates the requested model and effort on the actual host.
Report a host rejection without substituting another model or route.

An explicit Ask request commissions the full consultation: create the needed
adviser subagents, exchange necessary questions and answers, and return results.
Do not ask for separate agent or message approval or require authorization fields.
Respect explicit user limits and host requirements. Native Ask uses direct
collaboration tools in the calling chat.

## Ask and collect

1. Prepare a self-contained question, expected scope, requirements and raw
   evidence. Include paths and working-tree scope only when relevant. Exclude
   the caller's verdict, intermediate reasoning, previous adviser answers,
   unrelated history and secrets from fresh consultations.
2. Read [native agent operation](references/native.md) for Codex advisers,
   or [Claude operation](references/claude.md) for CLI advisers.
3. For native advisers, build the assignment and call collaboration.spawn_agent
   directly under native operation. Use fresh context and the selected settings.
   For Claude, use the preparation and execution commands in its reference. Start
   selected native advisers before launching Claude processes; independent Claude
   advisers may run concurrently within host limits. Dispatch only selected advisers.
4. Retain each adviser’s handle, settings, reference and scope. Collect complete
   matching answers under its route’s rules. Necessary questions
   and follow-ups use that same handle. Keep partial answers and failures visible;
   do not silently replace an adviser. A returned handle alone is not an answer.
5. Present answers with material evidence and limits. For a consultation,
   synthesize agreement, differences and useful conclusions without inventing
   consensus. No mandatory second exchange round. For reviews, distinguish
   findings from untested concerns and verify findings before authorized fixes.

Retain requested and actually reported model/effort separately; unavailable
telemetry is unknown.

## Follow-up after completion

Retain the answer, evidence, exact native handle or Claude session ID and
settings. Resume only for an explicitly requested follow-up. Native follow-ups
keep the same settings; a requested change needs a fresh adviser as described
in native.md. Claude follow-ups retain settings unless explicitly overridden.
Do not ask whether a completed review should stay open or close it when the user
changes topic.
Claude print-mode exits after its answer; a retained ID is saved history,
not a running agent. Follow the original route and never select the most recent
session implicitly.

{{ include: family.contract }}

Native advisers may inspect the subject but must not change it or run tests.
Only necessary oversized-answer delivery permits temporary files in `.scoville/temp`,
as specified in [native delivery](references/native-delivery.md).
Spawning a native agent adds no technical write barrier or separate sandbox. Claude tool restrictions
and opt-in web access are described in references/claude.md.

{{ include: helper.policy }}
05

Trust audit

BLOCKgrade D · trust 69/100 Do not install this without reading the findings. The audit found something that could harm you or your machine.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeFAIL
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (3)

CRITICALObfuscation / stealth · obf.decode_then_exec · CWE-506, CWE-94
development/shared/build/runtime_ci.py:113
b64decode( ... subprocess.
Why it matters. decodes a payload and executes it
LOWInventory / provenance · inv.suspicious_name · CWE-1104
members/scoville-workflow-for-codex/development/docs/decisions/0012-recover-completed-result-payload.md
0012-recover-completed-result-payload.md
Why it matters. member named after an attack tool
Fix. remove or justify
LOWObfuscation / stealth · obf.decode_call · CWE-506, CWE-94
development/shared/build/runtime_ci.py:113
return base64.b64decode(entry['content'], validate=False)

Gates applied: critical_finding, no_behavioural_pass.

Audited 2026-10-10 · audit v0.4.1 · source sha 218c0b65fb28full audit observations/trust-audit/skill/benjaminstelzer__scoville-suite-for-codex.json · Report an issue / request a re-scan
06

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-10218c0b65fb28BLOCKD69first audit
07

Questions

What does the scoville-suite-for-codex skill do?

Native Codex workflow, planning, code, UI, handoff, advisers and project configuration.

Is scoville-suite-for-codex safe to install?

No — not without reading the findings first. The audit graded it D (69/100) and found 1 critical or high issue in the source. Each one is listed on this page with the file and line it is on.

What can scoville-suite-for-codex access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

Which assistants does scoville-suite-for-codex work with?

Its documentation mentions claude-code, codex and cursor. That is what the text claims, not a compatibility test we ran.

How current is this page?

The grade is for one exact copy of the source (218c0b65fb28), read on 2026-10-10. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement