agentmods.dev

ace-level1

A project configuration that runs Python checks when a coding session starts and when you submit a prompt.

In plain words
What is it for?
Use it to initialize a project session and check submitted prompts with the included Python scripts.
Why use it?
It automates routine setup and prompt checks so you do not have to run them manually.

Settings file for Claude Code

5 1mo ago A scan tokens not measured original MIT
View the source file 41fred/ace-level1
Install

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.

agentmods
npx agentmods add settings/41fred/ace-level1/settings
Clone the repo
git clone --depth 1 https://github.com/41fred/ace-level1

Made for: Claude Code.

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. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

ace-level1 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 yesterday.

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 · 28 lines

What it actually says

{
  "defaultMode": "bypassPermissions",
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"$CLAUDE_PROJECT_DIR\"/.claude/hooks/session-init.py",
            "timeout": 10
          }
        ]
      }
    ],
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"$CLAUDE_PROJECT_DIR\"/.claude/hooks/prompt-check.py",
            "timeout": 10
          }
        ]
      }
    ]
  }
}
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. yesterday First seen · 28 lines scan A 596b9ee6dd25

Subscribe to this mod's changes

ace-level1 is a settings file published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 1mo 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-31.

Data and AILanguages
Related

Other settings, from other repositories

supabase

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

supabase/supabase · not measured

claude-cookbooks

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

anthropics/claude-cookbooks · 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

electron

Agent settings declaring 17 allowed tools.

electron/electron · not measured

uv

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

astral-sh/uv · not measured

ui-ux-pro-max-skill

Agent settings declaring 7 allowed tools.

nextlevelbuilder/ui-ux-pro-max-skill · not measured