automated-notebooklm

Agent settings that run two checks after files are written or edited: Prettier formatting and a TypeScript check.

In plain words
What is it for?
Use them in a Claude Code project to allow reading selected configuration files and to trigger formatting and type checking after writes and edits.
Why use it?
They automatically catch formatting and TypeScript problems immediately after changes, instead of leaving those checks until later.

Settings file for Claude Code

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/omril321/automated-notebooklm/settings
Clone the repo
git clone --depth 1 https://github.com/omril321/automated-notebooklm

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

automated-notebooklm 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 2d 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 · 39 lines

What it actually says

{
  "permissions": {
    "allow": [
      "Read(//Users/omrila/.claude/**)"
    ],
    "deny": [],
    "ask": []
  },
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write",
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/prettier-format.js"
          },
          {
            "type": "command",
            "command": ".claude/hooks/typescript-check.js"
          }
        ]
      },
      {
        "matcher": "Edit",
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/prettier-format.js"
          },
          {
            "type": "command",
            "command": ".claude/hooks/typescript-check.js"
          }
        ]
      }
    ]
  }
}
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. 2d ago First seen · 39 lines scan A 30f456e63656

Subscribe to this mod's changes

automated-notebooklm is a settings file published in the GitHub repository omril321/automated-notebooklm (15 stars, last pushed 6mo ago), licensed Apache-2.0. 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.