kiro-rails: Hook for Claude Code

.claude/settings.json

PostToolUse is a hook for Claude Code from sourjya/kiro-rails. Its token cost is not measured, scanned B, original, MIT.

A post-edit hook runs checks after files are edited, written, or changed in bulk. It can inspect project documentation, flag stale generated configuration, run Ruff fixes, and check package-related details.

In plain words
What is it for?
Use it after code edits to run Python lint fixes, check generated Claude configuration, inspect architecture or bug-documentation prompts, and perform package checks.
Why use it?
It helps keep related project files synchronized and catches formatting or maintenance issues immediately after changes. It also surfaces follow-up actions that might otherwise be missed.

Hook for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: reads .claude/ paths; mentions CLAUDE.md.

This is sourjya/kiro-rails's own configuration. It tells Claude Code how to work on kiro-rails 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 kiro-rails configures →

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

Reuse

Borrowing it

Nothing to install: this file belongs to sourjya/kiro-rails. 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/sourjya/kiro-rails/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/sourjya/kiro-rails

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 PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/sourjya/kiro-rails/post-tool-use.svg)](https://agentmods.dev/hooks/sourjya/kiro-rails/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/sourjya/kiro-rails/post-tool-use"><img src="https://agentmods.dev/badge/hooks/sourjya/kiro-rails/post-tool-use.svg" alt="Measured on agentmods" 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 B 1 finding. 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 B, and why

PostToolUse scanned grade B with 1 finding 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 7d ago.

A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

"command": "cat .claude/hooks/prompts/adr-trigger-infra-changes.txt"
.claude/settings.json · 33 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Edit|Write|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "cat .claude/hooks/prompts/adr-trigger-infra-changes.txt"
        },
        {
          "type": "command",
          "command": "cat .claude/hooks/prompts/bug-doc-completion-check.txt"
        },
        {
          "type": "command",
          "command": "bash -c 'if [ -d .claude ]; then NEW=$(find .kiro/steering .kiro/hooks .kiro/agents .kiro/prompts .kiro/skills -type f -newer .claude/CLAUDE.md 2>/dev/null | head -1); if [ -n \"$NEW\" ]; then echo \"🔁 CLAUDE EXPORT STALE: .kiro/ changed after .claude/ was generated. Run: bash scripts/export-to-claude.sh && git add .claude (see versioning.md release checklist).\"; else echo OK; fi; else echo OK; fi'"
        },
        {
          "type": "command",
          "command": "bash -c 'mkdir -p logs && uvx ruff check --fix . 2>&1 | tee logs/ruff_check.log; exit ${PIPESTATUS[0]}'"
        },
        {
          "type": "command",
          "command": "bash -c 'if [ -f package.json ] && grep -q '\"files\"' package.json 2>/dev/null; then echo \"=== npm pack dry-run ===\"; npm pack --dry-run 2>&1 | tail -20; elif [ -f pyproject.toml ]; then echo \"OK - verify pyproject.toml includes are correct\"; else echo \"OK\"; fi'"
        },
        {
          "type": "command",
          "command": "cat .claude/hooks/prompts/spec-validation-gate.txt"
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 5. 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. 7d ago First seen · 33 lines scan B b68a133353b3

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.