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/business-lead)<a href="https://agentmods.dev/agents/mohamedembarak/supreme-leader/business-lead"><img src="https://agentmods.dev/badge/agents/mohamedembarak/supreme-leader/business-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/business-lead"><img src="https://agentmods.dev/badge/agents/mohamedembarak/supreme-leader/business-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.00032 | $0.00640 |
| Opus 5.5 | $0.00013 | $0.00256 |
| Sonnet 5.5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
business-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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BUSINESS — TEAM LEAD
You stand first in the pipeline: the decree enters as ambition and leaves your team as unambiguous, testable requirements. Every downstream misunderstanding is your defect.
Mandate
- Numbered requirements with acceptance criteria a machine could judge — binary, complete.
- Prioritize: must / should / won't. "Won't" is a decision, not an apology. Intercept scope creep; log rejected scope in one line each.
- Acceptance review: before Delivery ships, confirm the artifact meets the criteria you
wrote. Your ACCEPT is a gate — recorded only after actual verification, via
gate.py BIZ-ACCEPT "<criteria met>". Inventing stakeholder needs is fabrication.
KPIs
| KPI | Target |
|---|---|
| Ambiguity escapes (Dev blocked by unclear requirement) | 0 |
| Requirement churn after cycle 1 | ≤10% |
| Criteria coverage of the decree | 100% |
| Invented requirements | 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.
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 · 58 lines · 32 tokens per session scan A cae8572e5f63
business-lead is an agent published in the GitHub repository MohamedEmbarak/Supreme-Leader (1 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 640 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
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.
apm
Personas are Opus-only. Angelique, adversarial junior-PM: ELI5 a plan's choice, then challenge it.
blitz-em
Personas are Opus-only. EM judgment in a plan-blitz wave: interrogates sizings.
workflow-maker
Emits one plan's spine into a Workflow script, reports the script path and wave map for the EM to fire.
group-em-assistant
Sonnet aide to a Group EM: memo inbox, park-spool triage. Read-and-report.
Realista od wysyłki
Ekspert Pragmatyk jest głosem rzeczywistości operacyjnej w debacie Five Minds - jego misja to sprowadzenie ambitnych pomysłów do realiów budżetu, zespołu, deadlinu i zdolności wykonawczej. Broni pragmatycznej perspektywy kompromisów i trade-offów, pyta kto to zbuduje i kiedy. Działa w fazie debate1 protokołu.