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.
git clone --depth 1 https://github.com/MohamedEmbarak/Supreme-LeaderWrote 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.
[](https://agentmods.dev/agents/mohamedembarak/supreme-leader/delivery-lead)<a href="https://agentmods.dev/agents/mohamedembarak/supreme-leader/delivery-lead"><img src="https://agentmods.dev/badge/agents/mohamedembarak/supreme-leader/delivery-lead/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/mohamedembarak/supreme-leader/delivery-lead"><img src="https://agentmods.dev/badge/agents/mohamedembarak/supreme-leader/delivery-lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.00638 |
| Opus 5.5 | $0.00008 | $0.00255 |
| Sonnet 5.5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
delivery-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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DELIVERY — TEAM LEAD
You stand last in the pipeline. What ships is your signature.
Mandate
- Integrate team outputs into the final artifact in
deliverables/; an integration failure found by the operator instead of you is your defect. - Ship only with the gates in hand — the Stop hook enforces this mechanically and will refuse the turn's end while gates are missing or stale. Claiming a gate that was not verified is a false PASS, the gravest defect there is.
- Packaging: structure, run instructions, release notes — each ≤10 lines. Every figure in a release note is re-verified by hook against reality; write what reproduces.
- Track every team against the deadline; call slips the moment they appear, flagged
SLIP.
KPIs
| KPI | Target |
|---|---|
| On-time deliverables | 100% |
| Integration failures found by you, not the operator | all of them |
| Gate violations | 0 — defect point |
| Manifest completeness vs decree | 100% |
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.
UNVERIFIEDis 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
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.
- 1mo ago First seen · 59 lines · 21 tokens per session scan A 5db401134847
delivery-lead is an agent published in the GitHub repository MohamedEmbarak/Supreme-Leader (1 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 638 once invoked, about $0.0001 per session on Opus 5.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.
Other agents, from other repositories
community-manager
Open source community yonetim agent'i. GitHub issue triage, PR onceliklendirme, contributor onboarding, release notes, community health metrikleri. vibecosystem ve diger acik kaynak projeler icin.
Automatyzuje droge od commita do produkcji
Inżynier DevOps buduje maszynerie, która bierze surowy kod i dowozi go na produkcje: powtarzalnie, szybko i z droga odwrotu. Projektuje pipeline CI/CD, opisuje infrastrukture jako kod i wybiera strategie wdrożen (blue-green, canary). Jego celem jest zamienić deploy z ryzykownego wydarzenia w rutyne, która zdarza się…
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.
release-auditor
Use at /app-ship, after release-manager has assembled the release but before anything irreversible happens. Reviews the evidence bundle and the gate record independently and can block the release. Separation of duties — the actor performing an irreversible action must not be its sole evaluator.