cds-autonomous 100/100

Is cds-autonomous safe to install?

SaferSkills independently audited cds-autonomous (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

vendor/cds-workflow/skills/cds-autonomous/SKILL.md · 1 file

vendor/cds-workflow/skills/cds-autonomous/SKILL.md1.9 KB · Markdown

name: cds-autonomous

description: "Run all remaining phases autonomously — discuss→plan→execute per phase"

argument-hint: "[--from N] [--to N] [--only N] [--interactive]"

allowed-tools:

- Read

- Write

- Bash

- Glob

- Grep

- AskUserQuestion

- Task

- Agent

<objective> Execute all remaining milestone phases autonomously. For each phase: discuss → plan → execute. Pauses only for user decisions (grey area acceptance, blockers, validation requests).

Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase command. After all phases complete: milestone audit → complete → cleanup.

Creates/Updates:

.planning/STATE.md — updated after each phase
.planning/ROADMAP.md — progress updated after each phase
Phase artifacts — CONTEXT.md, PLANs, SUMMARYs per phase

After: Milestone is complete and cleaned up. </objective>

<execution_context> @$HOME/.claude/cds-workflow/workflows/autonomous.md @$HOME/.claude/cds-workflow/references/ui-brand.md </execution_context>

<context> Optional flags:

--from N — start from phase N instead of the first incomplete phase.
--to N — stop after phase N completes (halt instead of advancing to next phase).
--only N — execute only phase N (single-phase mode).
--interactive — run discuss inline with questions (not auto-answered), then dispatch plan→execute as background agents. Keeps the main context lean while preserving user input on decisions.

Project context, phase list, and state are resolved inside the workflow using init commands (gsd-tools.cjs init milestone-op, gsd-tools.cjs roadmap analyze). No upfront context loading needed. </context>

<process> Execute the autonomous workflow from @$HOME/.claude/cds-workflow/workflows/autonomous.md end-to-end. Preserve all workflow gates (phase discovery, per-phase execution, blocker handling, progress display). </process>

cds-autonomous— agent skill

Is cds-autonomous safe to install?

Audit the pieces. Scan the whole. Decide.