dev-crew

A delivery system that assembles role-specific software agents and passes work through a gated sequence, such as planning, coding, testing, and deployment.

In plain words
What is it for?
It helps coordinate coding tasks with configurable agent roles, model levels, handoffs, and a learning loop for each repository.
Why use it?
It separates responsibilities and checkpoints so unfinished or unverified work is less likely to move to the next stage unnoticed.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add alexmond/alexmskills
agentmods
npx agentmods add plugins/alexmond/alexmskills/dev-crew
Clone the repo
git clone --depth 1 https://github.com/alexmond/alexmskills

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

dev-crew scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/dev-crew/.claude-plugin/plugin.json · 20 lines

What it actually says

{
  "name": "dev-crew",
  "description": "A self-evolving delivery crew: it composes a task-fit roster of role subagents (each on its own model tier) and runs them as a gated relay to deliver a target, with editable rosters and a per-repo learning loop. architect → dev → qa → deployer is just one example lineup.",
  "version": "1.3.0",
  "author": {
    "name": "Alex Mondshain",
    "email": "[email protected]"
  },
  "homepage": "https://www.alexmond.org/alexmskills/",
  "repository": "https://github.com/alexmond/alexmskills",
  "license": "MIT",
  "keywords": [
    "agents",
    "orchestration",
    "delivery",
    "relay",
    "self-evolving"
  ]
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 20 lines scan A 77ae7add56c0

Subscribe to this mod's changes

dev-crew is a plugin published in the GitHub repository alexmond/alexmskills (6 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.