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 commands/rungchan2/frontend-skills/check-data-layergit clone --depth 1 https://github.com/rungchan2/frontend-skillsWrote 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/commands/rungchan2/frontend-skills/check-data-layer)<a href="https://agentmods.dev/commands/rungchan2/frontend-skills/check-data-layer"><img src="https://agentmods.dev/badge/commands/rungchan2/frontend-skills/check-data-layer.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.1 | $0.00000 | $0.01237 |
| Opus 5 | $0.00000 | $0.00619 |
| Sonnet 5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00124 |
Grade A, and why
check-data-layer 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 6d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Data Layer Violations
Scan the codebase for violations of the data layer separation architecture and report them.
What to Check
1. Component violations:
- Search for
import.*createClient.*from.*@/lib/supabase/clientin component files - Search for
useQueryoruseMutationdefined directly in component files (not imported)
2. Hook violations:
- Search for
createClient()calls in/hooks/files - Hooks should only import service functions, not call Supabase directly
3. Service organization:
- Check if service functions are properly organized in
/lib/services/ - Verify proper file naming:
{table-name}.tsor{feature-name}-service.ts
4. TypeScript violations:
- Functions without explicit return types
- Async functions without
Promise<T>return types - Inline type definitions (not imported from
/types/) - Usage of
anytype - Duplicate type definitions that already exist in
/types/
Search Patterns
Use Grep to find violations:
# === Architecture Violations ===
# Find components importing Supabase client
grep -r "import.*createClient.*from.*@/lib/supabase/client" app/ components/ --include="*.tsx" --include="*.ts"
# Find inline queries in components (check for useQuery not from import)
grep -r "useQuery({" app/ components/ --include="*.tsx" -A 3
# Find createClient in hooks (should be in services only)
grep -r "createClient()" hooks/ --include="*.ts" --include="*.tsx"
# Find service functions not in /lib/services/
grep -r "from('.*')" app/ components/ hooks/ --include="*.tsx" --include="*.ts"
# === TypeScript Violations ===
# Find functions without return types (async functions)
grep -rE "export async function [a-zA-Z]+\([^)]*\)\s*{" lib/services/ hooks/ --include="*.ts" --include="*.tsx"
# Find functions without return types (regular functions)
grep -rE "export function [a-zA-Z]+\([^)]*\)\s*{" lib/services/ hooks/ --include="*.ts" --include="*.tsx"
# Find usage of 'any' type
grep -r ": any" lib/services/ hooks/ --include="*.ts" --include="*.tsx"
# Find inline type definitions (type/interface not in /types/)
grep -r "^type [A-Z]" app/ components/ lib/services/ hooks/ --include="*.ts" --include="*.tsx"
grep -r "^interface [A-Z]" app/ components/ lib/services/ hooks/ --include="*.ts" --include="*.tsx"
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.
- 6d ago First seen · 154 lines · 0 tokens per session scan A e6a0e3878bec
check-data-layer is a command published in the GitHub repository rungchan2/frontend-skills (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,237 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-31.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.