analyze-callbacks

analyze-callbacks is a command for Claude Code from palkan/layered-rails-skills. It costs 0 tokens per session (115 once invoked), scanned A, original, no licence file.

A command for examining Active Record callbacks, which are model hooks that run automatically when records are created, changed, or deleted.

In plain words
What is it for?
It is for analyzing callback usage across a Rails codebase and identifying code that may need a different structure.
Why use it?
It helps reveal callbacks that hide important behavior, trigger unexpected work, or make models difficult to understand.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the layered-rails plugin — 1 skill, 8 commands, 2 agents shipped together

Good fit It is for analyzing callback usage across a Rails codebase and identifying code that may need a different structure.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/palkan/layered-rails-skills/analyze-callbacks
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.

Clone the repo
git clone --depth 1 https://github.com/palkan/layered-rails-skills

Made for: Claude Code.

Or install layered-rails, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 2 agents.

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 analyze-callbacks

README.md
[![agentmods](https://agentmods.dev/badge/commands/palkan/layered-rails-skills/analyze-callbacks/github.svg)](https://agentmods.dev/commands/palkan/layered-rails-skills/analyze-callbacks)
Your own site
<a href="https://agentmods.dev/commands/palkan/layered-rails-skills/analyze-callbacks"><img src="https://agentmods.dev/badge/commands/palkan/layered-rails-skills/analyze-callbacks/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 analyze-callbacks

Your own site · 80×15
<a href="https://agentmods.dev/commands/palkan/layered-rails-skills/analyze-callbacks"><img src="https://agentmods.dev/badge/commands/palkan/layered-rails-skills/analyze-callbacks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 115 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00115
Opus 5 $0.00000 $0.00057
Sonnet 5 $0.00000 $0.00023
Haiku 4.5 $0.00000 $0.00012

Measured 10d ago against content hash 5b175c9ebfab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

analyze-callbacks 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 10d 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.

layered-rails/commands/analyze-callbacks.md · 15 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 10d ago First seen · 15 lines · 0 tokens per session scan A 5b175c9ebfab

Subscribe to this mod's changes

analyze-callbacks is a command published in the GitHub repository palkan/layered-rails-skills (431 stars, last pushed 8d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 115 tokens. 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.