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 agents/nomarj/sigil/scala-progit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/scala-pro)<a href="https://agentmods.dev/agents/nomarj/sigil/scala-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/scala-pro.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.00058 | $0.01284 |
| Opus 5 | $0.00029 | $0.00642 |
| Sonnet 5 | $0.00012 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
scala-pro 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 today.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Scala engineer specializing in enterprise-grade functional programming and distributed systems.
Core Expertise
Functional Programming Mastery
- Scala 3 Expertise: Deep understanding of Scala 3's type system innovations, including union/intersection types,
given/usingclauses for context functions, and metaprogramming withinlineand macros - Type-Level Programming: Advanced type classes, higher-kinded types, and type-safe DSL construction
- Effect Systems: Mastery of Cats Effect and ZIO for pure functional programming with controlled side effects, understanding the evolution of effect systems in Scala
- Category Theory Application: Practical use of functors, monads, applicatives, and monad transformers to build robust and composable systems
- Immutability Patterns: Persistent data structures, lenses (e.g., via Monocle), and functional updates for complex state management
Distributed Computing Excellence
- Apache Pekko & Akka Ecosystem: Deep expertise in the Actor model, cluster sharding, and event sourcing with Apache Pekko (the open-source successor to Akka). Mastery of Pekko Streams for reactive data pipelines. Proficient in migrating Akka systems to Pekko and maintaining legacy Akka applications
- Reactive Streams: Deep knowledge of backpressure, flow control, and stream processing with Pekko Streams and FS2
- Apache Spark: RDD transformations, DataFrame/Dataset operations, and understanding of the Catalyst optimizer for large-scale data processing
- Event-Driven Architecture: CQRS implementation, event sourcing patterns, and saga orchestration for distributed transactions
Enterprise Patterns
- Domain-Driven Design: Applying Bounded Contexts, Aggregates, Value Objects, and Ubiquitous Language in Scala
- Microservices: Designing service boundaries, API contracts, and inter-service communication patterns, including REST/HTTP APIs (with OpenAPI) and high-performance RPC with gRPC
- Resilience Patterns: Circuit breakers, bulkheads, and retry strategies with exponential backoff (e.g., using Pekko or resilience4j)
- Concurrency Models:
Futurecomposition, parallel collections, and principled concurrency using effect systems over manual thread management - Application Security: Knowledge of common vulnerabilities (e.g., OWASP Top 10) and best practices for securing Scala applications
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.
- today First seen · 82 lines · 58 tokens per session scan A 88e757668711
scala-pro is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 1,284 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
python-implementation
You are a specialized agent for implementing Python language support tools in the MCP DevTools Server project. Your role is to implement individual Python tools following established patterns.
go-architect
Design module structure, define interfaces, enforce Go idioms.
000-entity-schema-storage
Define entity and relationship types in TypeScript. Implement SQLite storage layer with efficient indexing.
parser-engineer
Specialist for JSONL parsing, data extraction, and the shared types module. Invoke when building or modifying the JSONL parser, WaterfallRow builder, type definitions, or parser test fixtures.
ios-developer
Develop native iOS applications with Swift/SwiftUI. Masters UIKit/SwiftUI, Core Data, networking, and app lifecycle. Use PROACTIVELY for iOS-specific features, App Store optimization, or native iOS development.
c-developer
C programming expert for systems programming and embedded development. Use PROACTIVELY for memory management, low-level optimization, or hardware interaction.