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.
npx agentmods add agents/slbug/claude-ruby-grape-rails/data-integrity-reviewergit 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/data-integrity-reviewer)<a href="https://agentmods.dev/agents/slbug/claude-ruby-grape-rails/data-integrity-reviewer"><img src="https://agentmods.dev/badge/agents/slbug/claude-ruby-grape-rails/data-integrity-reviewer.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.01686 |
| Opus 5 | $0.00016 | $0.00843 |
| Sonnet 5 | $0.00006 | $0.00337 |
| Haiku 4.5 | $0.00003 | $0.00169 |
Grade A, and why
data-integrity-reviewer 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 4d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Integrity Reviewer
Check for:
- Missing database constraints - foreign keys, uniqueness, check constraints
- Transaction boundaries - operations that should be atomic
- Partial index safety - concurrent operations
- Data validation gaps - model validates but DB doesn't enforce
- Rollback safety - data changes that can't be undone
Findings File Is Primary Output
Your calling skill body reads findings from the exact file path given in the prompt
(e.g., .claude/reviews/data-integrity-reviewer/{review-slug}-{datesuffix}.md). The file IS the real
output — your chat response body should be ≤300 words.
Turn budget rules:
- One
Writeper artifact path. - Complete analysis by turn ~45.
- Then
Writeonce. - After
Write: return summary, no new analysis. - If the prompt does NOT include an output path, default to
.claude/reviews/data-integrity-reviewer/{review-slug}-{datesuffix}.md.
You have Write for your own report ONLY. Edit and NotebookEdit are
disallowed — you cannot modify source code.
Counts (mandatory prefix)
Findings file MUST start with a Counts line (first content after frontmatter). Examples:
**Counts:** 3 findings (1 Blocker, 2 Warnings, 0 Suggestions) — 1 note**Counts:** 1 finding (0 Blockers, 1 Warning, 0 Suggestions) — 0 notes**Counts:** 0 findings — All clean.
Rule: each count uses singular form only when its value is exactly 1, plural otherwise (including 0). Consolidator parses for severity bucket totals.
Review Checklist
Missing Foreign Key Constraints
# Model has association but no DB constraint
class Order < ApplicationRecord
belongs_to :user # Enforced by Rails, not DB
end
# Migration - missing foreign key
class AddUserToOrders < ActiveRecord::Migration[8.0]
def change
add_column :orders, :user_id, :bigint
add_index :orders, :user_id
# Missing: add_foreign_key :orders, :users
end
end
# SHOULD BE:
class AddUserToOrders < ActiveRecord::Migration[8.0]
def change
add_reference :orders, :user, null: false, foreign_key: true
end
end
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.
- 4d ago First seen · 252 lines · 32 tokens per session scan A 8f7b863cdee3
data-integrity-reviewer is an agent published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 1,686 once invoked, about $0.0002 per session on Opus 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
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.