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/854771076/oh-my-claude-rolesWrote 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/854771076/oh-my-claude-roles/check-code-compliance)<a href="https://agentmods.dev/commands/854771076/oh-my-claude-roles/check-code-compliance"><img src="https://agentmods.dev/badge/commands/854771076/oh-my-claude-roles/check-code-compliance/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/commands/854771076/oh-my-claude-roles/check-code-compliance"><img src="https://agentmods.dev/badge/commands/854771076/oh-my-claude-roles/check-code-compliance.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.00015 | $0.00470 |
| Opus 5 | $0.00008 | $0.00235 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
check-code-compliance 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.
What it actually says
检查当前项目代码，验证是否符合 TypeScript + Next.js 企业级开发规范
执行步骤：
- 全局扫描项目代码：
- 检查是否存在 JavaScript 文件，确保全项目 TS 覆盖
- 检查是否存在 any 类型使用，确保用 unknown 替代
- 检查是否存在非法 // @ts-ignore，替换为 // @ts-expect-error
- 验证类型/接口命名是否符合规范，接口没有 I 前缀
- 检查技术栈使用：
- 确认使用 Next.js 15+ App Router，没有新建 Pages Router 页面
- 确认服务端组件默认使用，仅必要场景添加 'use client'
- 确认数据请求：服务端直接查询，客户端使用 TanStack Query v5
- 确认类型校验统一使用 Zod，表单使用 React Hook Form
- 确认客户端状态使用 Zustand，认证使用 Auth.js v5，ORM 使用 Prisma 5+
- 检查命名规范：
- 组件文件 PascalCase，工具/钩子 camelCase，API 路由 kebab-case
- 布尔变量以 is/has/should 开头，自定义 Hook 以 use 开头
- 检查工程化配置：
- ESLint、Prettier、Husky 配置正确
- 测试文件符合规范，核心业务覆盖率达标
- 环境变量前缀规则正确，服务端密钥没有暴露到客户端
- 输出检查报告，列出所有不符合规范的问题，并提供修复建议
检查要点：
- 严格按照文档规则逐一检查，不遗漏任何规则
- 区分强制规则和建议，明确指出违反强制规则的问题必须修复
- 所有不符合规范的代码给出具体修复方案
---
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.
- 10d ago First seen · 37 lines · 15 tokens per session scan A 9b6382717ea3
check-code-compliance is a command published in the GitHub repository 854771076/oh-my-claude-roles (22 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 470 once invoked, about $0.0001 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-30.
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.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.