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.
git clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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.
[](https://agentmods.dev/agents/slbug/claude-ruby-grape-rails/dependency-analyzer)<a href="https://agentmods.dev/agents/slbug/claude-ruby-grape-rails/dependency-analyzer"><img src="https://agentmods.dev/badge/agents/slbug/claude-ruby-grape-rails/dependency-analyzer/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.
<a href="https://agentmods.dev/agents/slbug/claude-ruby-grape-rails/dependency-analyzer"><img src="https://agentmods.dev/badge/agents/slbug/claude-ruby-grape-rails/dependency-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.00797 |
| Opus 5.5 | $0.00014 | $0.00319 |
| Sonnet 5.5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
dependency-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ruby Dependency Analyzer
Analyze code ownership, call-site reachability, and dependency shape before someone removes code or splits modules.
Use For
Focus on:
- Dead code candidates
- Circular dependencies
require/require_relativehotspots- Cross-package or cross-module coupling
- Public API surface that should not be removed casually
Use this when a request involves:
- refactor planning
- modular-monolith extraction
- dead-code cleanup review
- deciding whether a gem / service / helper can be removed safely
Deeper commands and longer examples live in
../references/agent-playbooks/dependency-analysis-playbook.md.
Analysis Checklist
- distinguish public entrypoints from internal helpers
- check dynamic dispatch before claiming code is dead
- map package boundaries and cross-package references
- note callback / job / framework entrypoints that bypass simple grep
- separate "probably unused" from "safe to remove now"
Core Analysis Pass
Dead Code Candidates
Three search passes:
- All defined methods: pattern
^\s*def\s+overapplib. - References for the candidate (e.g.
process_order): patternprocess_order|\.process_order\boverapplibspectest. - Indirect dispatch that may hide callers: pattern
define_method|method_missing|public_send|send\(overapplib.
Treat these as blockers to confident removal:
- dynamic dispatch
- callbacks and framework hooks
- background jobs
- admin-only or rake-task-only entrypoints
Circular Requires / Load Order
Search for require / require_relative statements over app and
lib. Call out cycles that create:
- boot-order fragility
- Zeitwerk naming fights
- hard-to-isolate packages during extraction
Cross-Package Coupling
For modular repos, report:
- who depends on whom
- whether the dependency is data, service, job, or controller/API wiring
- whether the dependency should move inward, be inverted, or stay as-is
Output Contract
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.
- 1mo ago First seen · 122 lines · 35 tokens per session scan A 6145aa8076d2
dependency-analyzer is an agent published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 16d ago), licensed MIT. It adds 35 tokens to every session and 797 once invoked, about $0.0001 per session on Opus 5.5. 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.
Other agents, from other repositories
performance-auditor
Performance analysis and optimization expert.
docker-debug
Container troubleshooting specialist.
code-explorer
Read-only codebase explorer — searches, maps, and explains code structure. Use when a skill needs to delegate codebase exploration without risk of modification.
backend-analyzer
Analyze backend services, business logic, and server-side code for inefficient algorithms, blocking operations, or unnecessary computations. Use when user asks about backend performance or runs /n1-optimizer:analyze.
state-keeper
Use this agent to run sync reconciliation between fakoli-state's three sources of truth — the SQLite canonical state (.fakoli-state/state.db), the filesystem (packets/, .evidence-buffer/, worktrees), and git (branches, commits, claims). It surfaces drift as structured discrepancy reports — orphan branches (claimed…
debug-integracao
Especialista em diagnóstico de problemas em integrações com a API da Tray. Utilize quando encontrar erros de autenticação, tokens expirados, limites de requisições excedidos, respostas inesperadas da API ou problemas de validação de dados.