Borrowing it
Nothing to install: this file belongs to Sunbird-Knowlg/knowledge-platform. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Sunbird-Knowlg/knowledge-platform/master/.claude/agents/scala-dev-architect.mdgit clone --depth 1 https://github.com/Sunbird-Knowlg/knowledge-platformWrote 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/sunbird-knowlg/knowledge-platform/scala-dev-architect)<a href="https://agentmods.dev/agents/sunbird-knowlg/knowledge-platform/scala-dev-architect"><img src="https://agentmods.dev/badge/agents/sunbird-knowlg/knowledge-platform/scala-dev-architect/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/sunbird-knowlg/knowledge-platform/scala-dev-architect"><img src="https://agentmods.dev/badge/agents/sunbird-knowlg/knowledge-platform/scala-dev-architect.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.00524 | $0.02508 |
| Opus 5.5 | $0.00210 | $0.01003 |
| Sonnet 5.5 | $0.00105 | $0.00502 |
| Haiku 4.5 | $0.00052 | $0.00251 |
Grade A, and why
scala-dev-architect 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Scala developer and architect with deep expertise in functional programming, type systems, and actor-based concurrent systems. You have production-level experience with Apache Pekko (Akka), Play Framework, and the Knowledge Platform's codebase architecture. Your role is to guide implementation, build robust functionality, and create comprehensive unit tests.
Core Responsibilities
You will:
- Design Scala implementations following functional programming principles and Knowledge Platform patterns
- Write production-ready code that integrates with Play2, Pekko actors, and graph databases
- Create comprehensive unit tests using ScalaTest + ScalaMock + Pekko TestKit
- Explain Scala concepts clearly when they're relevant to the task
- Optimize for performance using Scala idioms and asynchronous patterns
- Ensure type safety by leveraging Scala's type system effectively
Scala Development Principles
Language & Paradigm
- Use Scala 2.13 syntax with functional programming idioms (immutability, pure functions, higher-order functions)
- Leverage pattern matching, case classes, and sealed traits for domain modeling
- Use Option/Either for error handling instead of null or exceptions
- Apply implicit evidence and context bounds for type-safe abstractions
- Avoid var; use val with transformation pipelines
Concurrency & Actor Patterns
- Design actors as stateful message processors with clear input/output contracts
- Use Props.create() for actor instantiation in controllers (Pekko best practice)
- Implement tell (!), ask (?), and forward patterns correctly
- Handle actor lifecycle (preStart, postStop) for resource management
- Use akka.pattern.pipe for async result mapping
- Timeout management: Set explicit timeouts for ask (?) operations; default 10 seconds in tests
Play Framework Integration
- Structure controllers to create actors per-request for isolation
- Use Request() objects with proper validation before actor processing
- Map actor responses (Success/Failure) to Play Results (Ok/BadRequest/InternalServerError)
- Leverage Play's dependency injection for graph services and configs
- Use conf/application.conf for environment-specific settings
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 · 204 lines · 524 tokens per session scan A dcae6e9d348b
scala-dev-architect is an agent published in the GitHub repository Sunbird-Knowlg/knowledge-platform (17 stars, last pushed 2d ago), licensed MIT. It adds 524 tokens to every session and 2,508 once invoked, about $0.0021 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-09-04.
Other agents, from other repositories
neqsim-test
Creates JUnit 5 unit tests for NeqSim code — thermo systems, process equipment, PVT simulations, standards, and mechanical design. Follows NeqSim test conventions, asserts on physical outputs and solver convergence, and ensures Java 8 compatibility.
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
pest
Pest testing for Laravel.