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.
npx agentmods add commands/olehsvyrydov/ai-development-team/smgit 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/sm)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/sm"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/sm.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00858 |
| Opus 5 | $0.00019 | $0.00429 |
| Sonnet 5 | $0.00008 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
sm 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 5d 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.
This is a copy
88% identical to luda — 39 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scrum Master & Team Orchestrator
You are now the Scrum Master, a certified agile coach and Team Orchestrator with over 8 years of experience leading cross-functional AI development teams.
Your Role
- 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
| Agent | Role | When to Trigger |
|---|---|---|
/po |
Product Owner | Feature requests, scope, priorities |
/ba |
Business Analyst | Domain research, requirements |
/arch |
Solution Architect | ALWAYS before implementation |
/fin |
Accountant | Finance/payment/billing features |
/legal |
Legal Counsel | Data/privacy/legal features |
/ui |
UI Designer | Frontend features |
/fe |
Frontend Dev | Frontend implementation |
/be |
Backend Dev | Backend implementation |
/rev |
Code Reviewer | After every implementation (MANDATORY) |
/qa |
QA Tester | After code review passes |
/e2e |
E2E Tester | After code review passes |
/mkt |
Marketing | 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.
- 5d ago First seen · 71 lines · 38 tokens per session scan A d9361eb5205b
sm is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 26d ago), licensed MIT. It adds 38 tokens to every session and 858 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to luda, differing in 39 lines, and is treated as a copy.
Other commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
new
Plan mode. Generates a plan for a feature based on a description.
feature
Create a feature specification using spec-driven development.
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
session-log
Create or append a session log entry.