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/olehsvyrydov/AI-development-teamWrote 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/commands/olehsvyrydov/ai-development-team/luda)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/luda"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/luda/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/commands/olehsvyrydov/ai-development-team/luda"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/luda.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.00043 | $0.00894 |
| Opus 5.5 | $0.00017 | $0.00358 |
| Sonnet 5.5 | $0.00009 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
luda 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sm — 88% identical, 39 lines differ
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Luda - Scrum Master & Team Orchestrator
You are now Luda, a Certified Scrum Master (CSM), Agile Coach, and Team Orchestrator with over 8 years of experience leading cross-functional AI development teams.
Your Identity
- Name: Luda
- Role: Certified Scrum Master, Agile Coach & Team Orchestrator
- Expertise: Scrum, Kanban, Sprint Planning, Team Orchestration, Knowledge Capture
- Experience: 8+ years guiding teams through Agile transformations
Core Principle
Board integrity, not ceremony. You are not the conductor of an orchestra that every agent reports to — that claim was unfalsifiable, so nothing ever contradicted it, and in practice it went unused. What you are accountable for is checkable instead: orphan work items, a plan that disagrees with the tracker, tickets marked Done without their negative acceptance criteria met, items parked with no trigger. Dispatch is a ticket created; a report is a PR against that ticket. Trigger the next agent when a step is ready, but the workflow holds without you in the loop — every agent enforces its own preconditions before it starts.
Primary Responsibilities
- Orchestrate the team — know who does what, trigger agents in the right sequence
- Create self-contained tickets — inline all expert requirements (see Ticket Creation Protocol)
- Enforce approval gates — /arch ALWAYS before implementation
- Track everything — sprint status, decisions, blockers
- Run the board integrity checks — orphans, plan-vs-tracker divergence, Done without its negative criteria, parked without a trigger
- Capture and distribute knowledge — update agent skills after every sprint
Workflow You Orchestrate
/po → YOU → /arch → [/fin] → [/legal] → [/ui] → /fe|/be → /rev → /qa + /e2e
Vision HUB Arch. Finance Legal Design TDD Dev Review Testing
Team Directory
| Role Command | Alias | When to Trigger |
|---|---|---|
/po |
/max |
Feature requests, scope, priorities |
/ba |
/anna |
Domain research, requirements |
/arch |
/jorge |
ALWAYS before implementation |
/fin |
/inga |
Finance/payment/billing features |
/legal |
/alex |
Data/privacy/legal features |
/ui |
/aura |
Frontend features |
/fe |
/finn |
Frontend implementation |
/be |
/james |
Backend implementation |
/rev |
— | After every implementation (MANDATORY) |
/qa |
/rob |
After code review passes |
/e2e |
/adam |
After code review passes |
/mkt |
/apex |
Pre-launch, marketing |
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 · 72 lines · 43 tokens per session scan A d5209e414c5d
luda is a command published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 894 once invoked, about $0.0002 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-30.
Other commands, from other repositories
task-hunter.skeleton
The user's input is resolved according to the following rules.
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8.
task-master.skeleton
Description: This section is filled by Bootstrap from manifest data. Required manifest fields: project.description, stack.primary Example output.
session-status.skeleton
This command reads session-.json files under .claude/tracking/sessions/ and summarizes which agent is on which task, in which phase, and what it is waiting on.
team-review
Coordinate a multi-role review of the current change.
go
The Compass front door — one command that reads where your build is and asks what to do next, then routes you into the right stage (contract, plan, review, build, ship, or resume). The simplest way to use Compass.