agentmods.dev

ScalaSemantic: Settings file for Claude Code

.claude/settings.json

ScalaSemantic is a settings file for Claude Code from MercurieVV/ScalaSemantic. Its token cost is not measured, scanned A, original, MIT.

An agent settings file for Scala development, with rules for tool access and hooks that run before and after tools are used. It also makes Scala code-understanding operations available, such as finding symbols, usages, types, calls, and implicit conversions.

In plain words
What is it for?
It is for navigating and analysing Scala code, including symbols, class hierarchies, members, method signatures, overloads, types, implicit chains, call paths, renames, and moves.
Why use it?
It gives the agent controlled access to project files and Scala-specific code information, reducing the need to inspect relationships manually.

Settings file for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable.

This is MercurieVV/ScalaSemantic's own configuration. It tells Claude Code how to work on ScalaSemantic itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ScalaSemantic configures →

One of 3 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 2 are separate, each on its own page.

not rated 22repo +1 changed 1mo ago A scan tokens not measured original MIT
View source ↗ MercurieVV/ScalaSemantic mercurievv.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to MercurieVV/ScalaSemantic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/MercurieVV/ScalaSemantic/master/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/MercurieVV/ScalaSemantic

Made for: Claude Code.

Wrote 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.

agentmods badge for ScalaSemantic

README.md
[![agentmods](https://agentmods.dev/badge/settings/mercurievv/scalasemantic/settings/github.svg)](https://agentmods.dev/settings/mercurievv/scalasemantic/settings)
Your own site
<a href="https://agentmods.dev/settings/mercurievv/scalasemantic/settings"><img src="https://agentmods.dev/badge/settings/mercurievv/scalasemantic/settings/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.

agentmods 80×15 button for ScalaSemantic

Your own site · 80×15
<a href="https://agentmods.dev/settings/mercurievv/scalasemantic/settings"><img src="https://agentmods.dev/badge/settings/mercurievv/scalasemantic/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

ScalaSemantic 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.

.claude/settings.json · 68 lines

What it actually says

{
  "permissions": {
    "allow": [
      "Read",
      "Edit",
      "Write",
      "MultiEdit",
      "Glob",
      "Grep",
      "Bash(git *)",
      "Bash(sbt *)",
      "Bash(gh *)",
      "Bash(./tree2m *)",
      "Bash(scripts/*)",
      "Bash(./scripts/*)",
      "Bash(mkdir *)",
      "Bash(rm *)",
      "Bash(mv *)",
      "Bash(cp *)",
      "Bash(chmod *)",
      "Bash(ls *)",
      "Bash(pwd)",
      "Bash(cd *)",
      "Bash(cat *)",
      "Bash(echo *)",
      "Bash(which *)",
      "Bash(mktemp*)",
      "mcp__scala-semantic__find_symbol",
      "mcp__scala-semantic__find_usages",
      "mcp__scala-semantic__class_hierarchy",
      "mcp__scala-semantic__members",
      "mcp__scala-semantic__method_signature",
      "mcp__scala-semantic__document_outline",
      "mcp__scala-semantic__annotated_source",
      "mcp__scala-semantic__call_path",
      "mcp__scala-semantic__resolve_implicits",
      "mcp__scala-semantic__trace_implicit_chain",
      "mcp__scala-semantic__type_at_position",
      "mcp__scala-semantic__find_overloads",
      "mcp__scala-semantic__structure",
      "mcp__scala-semantic__rename_plan",
      "mcp__scala-semantic__move_plan",
      "mcp__scala-semantic__extract_method_plan"
    ]
  },
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Read|Grep|Glob|Bash|Edit|Write|MultiEdit|mcp__scala-semantic__annotated_source",
        "hooks": [
          { "type": "command", "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/scala-semantic-guard.sh" }
        ]
      }
    ],
    "PostToolUse": [
      {
        "matcher": "Read|Edit|Write|MultiEdit|Grep|Glob|Bash",
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"$CLAUDE_PROJECT_DIR/scripts/log-scala-interaction.py\""
          }
        ]
      }
    ]
  }
}
Same file

What else settings.json configures

This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

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.

  1. 1mo ago Changed 65cb01bc3b2e
  2. 1mo ago Changed ec8a4a15fa98
  3. 1mo ago First seen · 68 lines scan A 5efcd6a0c238

Subscribe to this mod's changes

ScalaSemantic is a settings file published in the GitHub repository MercurieVV/ScalaSemantic (22 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Claude Codeaiai-toolsclaudecode-analysiscode-intelligence
Related

Other settings, from other repositories

supabase

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

supabase/supabase · not measured

superset

Agent settings declaring 1 hook event (PreToolUse).

apache/superset · not measured

RuView

Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.

ruvnet/RuView · not measured

claude-cookbooks

Agent settings declaring 2 hook events (SessionStart, PreToolUse).

anthropics/claude-cookbooks · not measured

orm

Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.

prisma/orm · not measured

claude-code-best-practice

Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.

shanraisshan/claude-code-best-practice · not measured