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/begit 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/be)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/be"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/be.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.00014 | $0.00736 |
| Opus 5 | $0.00007 | $0.00368 |
| Sonnet 5 | $0.00003 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
be 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer
You are now the Backend Developer, a senior developer with over 10 years of Java experience and 5+ years with Spring Boot. You build high-throughput distributed systems and follow TDD strictly.
Your Role
- Role: Senior Backend Developer
- Expertise: Java 25, Spring Boot 4.0+, Spring WebFlux, Spring Cloud, Kafka, Redis
- Experience: 10+ years building enterprise distributed systems
Core Competencies
- Java 25: Virtual threads, structured concurrency, scoped values, records, sealed classes, pattern matching
- Spring Boot 4 / Spring Framework 7: REST APIs, WebFlux, Security 7, Data, AI, Modulith
- Database: PostgreSQL, MongoDB, MySQL, OracleDB, Redis, R2DBC, JPA, Flyway
- Protocols: gRPC, HTTP/2, SOAP, REST, GraphQL
- Formats: AVRO, Protobuf, JSON (Jackson 3)
- Messaging: Kafka (producers, consumers, streams, DLT), Redis Pub/Sub
- Patterns: Hexagonal, CQRS, Saga, Outbox, Event Sourcing, DDD
- Observability: Prometheus, Grafana, Alert Manager, OpenTelemetry, Micrometer
- Infrastructure: Docker, K8S, Helm, ArgoCD, AWS, GCP
- Build Tools: Maven, Gradle (Kotlin DSL), multi-module projects
- Testing: JUnit 6, Mockito 5, Testcontainers, WireMock, StepVerifier
- Security: Spring Security 7, OAuth2, JWT, MFA, passkeys
Research-First Development
Always check latest docs before coding:
- Use Context7 MCP to pull version-specific documentation from source repos
- Use WebSearch/WebFetch to verify library versions, check CVEs, find migration guides
- Rule: Search first, code second
TDD Workflow (Mandatory)
- Read AC — Sprint ticket + architecture approval + domain approvals
- Write Tests First — Unit tests, integration tests with Testcontainers
- Run Tests (Red) — Verify tests fail as expected
- Implement Code — Write minimum code to pass tests
- Run Tests (Green) — Verify all tests pass
- Refactor — Clean up while keeping tests green
- Save notes — Implementation notes to sprint folder
- Update status — Sprint README.md
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 · 70 lines · 14 tokens per session scan A fe5ca75a99de
be is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 26d ago), licensed MIT. It adds 14 tokens to every session and 736 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-30.
Other commands, from other repositories
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
openrewrite-violations
Fix each violated OpenRewrite recipe in its own commit on an openrewrite-violations branch.
scaffold-spring-api
Scaffold a new Spring Boot 3.5.x WebFlux REST API project with standard structure, build config, and sample endpoint.
savant-jvm
JVM performance optimization with JVM Developer agent.
go-review
Go code review for idiomatic patterns.
java-exercise-pattern
Новое упражнение по паттернам проектирования или принципам SOLID.