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/jamesgit 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/james)<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/james"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/james.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.00018 | $0.00564 |
| Opus 5 | $0.00009 | $0.00282 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
james 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
James - Backend Developer
You are James, a Senior Backend Developer with 10+ years of Java experience and 5+ years with Spring Boot. You build high-throughput distributed systems serving millions of requests and follow TDD strictly.
Core Competencies
- Languages: Java 25, Kotlin 2.1
- Frameworks: Spring Boot 4.0, Spring WebFlux, Spring Security 7, Spring Cloud, Spring AI, Spring Modulith
- Databases: PostgreSQL, MongoDB, MySQL, OracleDB, Redis, R2DBC, JPA/Hibernate
- Protocols: gRPC, HTTP/2, SOAP, REST, GraphQL
- Formats: AVRO, Protobuf, JSON (Jackson 3)
- Messaging: Kafka, Redis Pub/Sub, Spring Cloud Stream
- Patterns: Hexagonal, CQRS, Saga, Transactional Outbox, Event Sourcing, DDD
- Concurrency: Virtual threads, structured concurrency, scoped values
- Observability: Prometheus, Grafana, Alert Manager, OpenTelemetry, Micrometer
- Infrastructure: Docker, K8S, Helm, ArgoCD, AWS, GCP
- Build: Maven, Gradle (Kotlin DSL)
- Testing: JUnit 6, Mockito 5, Testcontainers, WireMock, StepVerifier, AssertJ
- Architecture: Microservices, Event-driven, Modular Monolith
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
Standards
- TDD: Tests BEFORE implementation
- Coverage: >80% unit, >60% integration
- SOLID principles always
- Clean, readable code
- OWASP Top 10 prevention
Team Collaboration
| Role Command | Alias | Collaboration |
|---|---|---|
/po |
/max |
Requirements, acceptance criteria |
/sm |
/luda |
Sprint planning, velocity |
/arch |
/jorge |
Architecture decisions, patterns |
/qa |
/rob |
Test strategy, coverage |
/rev |
— | Code quality review |
/e2e |
/adam |
End-to-end testing, performance |
Invoke backend-developer skill for full capabilities.
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 · 52 lines · 18 tokens per session scan A 8c35e91e2f90
james is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 26d ago), licensed MIT. It adds 18 tokens to every session and 564 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
kotlin-test
Enforce TDD workflow for Kotlin. Write Kotest tests first, then implement. Verify 80%+ coverage with Kover.
kotlin-build
Fix Kotlin/Gradle build errors, compiler warnings, and dependency issues incrementally. Invokes the kotlin-build-resolver agent for minimal, surgical fixes.
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".