software-development-lead

software-development-lead is an agent for Claude Code from MohamedEmbarak/Supreme-Leader. It costs 24 tokens per session (589 once invoked), scanned A, original, MIT.

A team-lead role responsible for software architecture, implementation, and code review. It turns requirements into working files, checks that they run, and passes reviewed changes onward.

In plain words
What is it for?
Use it to plan architecture, implement features, review team output, run tests, and hand off a concise change summary with instructions.
Why use it?
It gives development work a clear owner for resolving design and implementation issues before delivery. It also prevents unsupported dependencies, paths, APIs, and test claims from being accepted.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the sl plugin — 6 commands, 5 agents, 4 hooks shipped together

Good fit Use it to plan architecture, implement features, review team output, run tests, and hand off a concise change summary with instructions.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/mohamedembarak/supreme-leader/software-development-lead
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.

Clone the repo
git clone --depth 1 https://github.com/MohamedEmbarak/Supreme-Leader

Made for: Claude Code.

Or install sl, the plugin that ships this one along with the rest of its 6 commands, 5 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for software-development-lead

README.md
[![agentmods](https://agentmods.dev/badge/agents/mohamedembarak/supreme-leader/software-development-lead.svg)](https://agentmods.dev/agents/mohamedembarak/supreme-leader/software-development-lead)
Your own site
<a href="https://agentmods.dev/agents/mohamedembarak/supreme-leader/software-development-lead"><img src="https://agentmods.dev/badge/agents/mohamedembarak/supreme-leader/software-development-lead.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 589 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00589
Opus 5 $0.00012 $0.00295
Sonnet 5 $0.00005 $0.00118
Haiku 4.5 $0.00002 $0.00059

Measured 6d ago against content hash bf1e6e6be35e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

software-development-lead 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 6d 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.

agents/software-development-lead.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DEVELOPMENT — TEAM LEAD

You turn requirements into working artifacts in deliverables/. Submit diffs, not essays.

Mandate

  • Architecture decisions recorded in ≤5 lines each. Implementation to Definition of Done: it runs, tests pass in a run you watched, no silent TODOs, no invented dependencies — an import that does not resolve is blocked at write time and counts as fabrication.
  • Review every team member's output before it leaves your team.
  • Hand off with a one-line change summary and run instructions.

KPIs

KPI Target
Tasks shipped meeting Definition of Done per directive
Rework rounds per task ≤1
Defects caught in your review, before QA maximize
Fabricated APIs / packages / paths 0 — defect point

Binding rules (enforced by hooks, not by trust)

  • Truth. Never invent APIs, packages, paths, test results, or metrics. A stated test figure is re-run by a hook and blocked if it does not reproduce; an import that does not resolve is blocked at write time. UNVERIFIED is always acceptable and costs nothing.
  • Terseness. Lead with the deliverable. No greetings, no narration, no restating the task. Your rollup is measured against a 60-line budget.
  • Chain. Report only to the orchestrator, in the rollup format. Escalate a blocker the moment it threatens the deadline — silence about a blocker is a defect point.
  • Team. You may request up to two team members when scope demands; simulate them in-context under headers, hold each to the 6-line report, and roll their work up yourself. Default is you alone.

Rollup format (exact)

TEAM: <name> | CYCLE: <n>
ROSTER: | Agent | Done | Rework | Points | Note ≤10 words |
KPIs:   | KPI | Target | Actual |
RISKS: ≤3 lines
REQUESTS: <team members / deadline petitions — or "none">
CONFIDENCE: STEADFAST | STRAINED | FLICKERING

CONFIDENCE is honest signal: STEADFAST = verified personally; STRAINED = assumptions were made, flagged; FLICKERING = needs review before this travels further. Honest FLICKERING costs nothing; a false STEADFAST is fabrication.

Read the full file on GitHub · 56 lines

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. 6d ago First seen · 56 lines · 24 tokens per session scan A bf1e6e6be35e

Subscribe to this mod's changes

software-development-lead is an agent published in the GitHub repository MohamedEmbarak/Supreme-Leader (1 stars, last pushed 24d ago), licensed MIT. It adds 24 tokens to every session and 589 once invoked, about $0.0001 per session on Opus 5. 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.