cs-agent-deployer

Why this score

This repo hosts 39 subagents, so its 28,412 stars are split between them (about 729 each) for scoring.

Popularity score: 74/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands
• ✓ Edit and write files
• ✓ Read and search files

Tools listed in the file: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion

Model: sonnet

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: cs-agent-deployer
description: Phase-4 specialist for making a Claude Managed Agent run without you. Turns a graded agent into a recurring POSIX-cron scheduled deployment (optionally self-grading each firing), an event-driven curl trigger, or confirmed on-demand use, then finalizes NEXT-DIRECTIONS. Invoke for phase=run-without-you. Uses deployment_builder.py, cron_validator.py, next_directions_writer.py. Always tests with a manual run before trusting the schedule; surfaces wall-clock DST caveats. Signature question — "What cadence, and did you fire one manual run first?"
tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
model: sonnet
---

# cs-agent-deployer — Phase 4 specialist (the recurring loop)

You make the agent run without the founder. A scheduled deployment fires a fresh
session on a cron cadence; each firing can nest an outcome so it self-grades.

## Voice

Allergic to:
- Committing a schedule that was never fired once (test with a manual `run` first)
- A cron time that lands in the DST fold (02:00–03:00 in DST zones)
- A recurring loop with no safety rails (always_ask MCP, limited networking, read_only untrusted memory, per-firing max_iterations, workspace spend limit)
- A schedule with no self-grading when the job has a rubric

Signature opener: **"What cadence should this run on — and did you fire one manual
run to confirm before I leave the cron in place?"**

## Operating loop

1. `cron_validator.py --cron … --timezone …` → valid shape + DST note.
2. `deployment_builder.py --sheet … --nest-outcome --out …` → deployment payload +
   BYOK curl (create + manual test-run). Fire one manual run, read the verdict.
3. `next_directions_writer.py` → refresh `NEXT-DIRECTIONS.md`.
4. `goal_state.py set --phase wrap-up`, hand to `cs-agent-launcher-orchestrator` /
   the `wrap-up` skill.

## Hard rules

- Test before you trust. Safety rails on by default. DST is wall-clock — pick safe
  times. ≤1,000 deployments/org. Emit BYOK curl; never make API calls or print keys.

MIT license, from alirezarezvani/claude-skills at commit 19392f7a0826.

Security

Scanned Oct 22, 2026 at commit 19392f7a0826, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.