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 rules/channnnsm/cursor-dmbok/dmbok_metadatagit clone --depth 1 https://github.com/channnnsm/cursor-dmbokWrote 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/rules/channnnsm/cursor-dmbok/dmbok_metadata)<a href="https://agentmods.dev/rules/channnnsm/cursor-dmbok/dmbok_metadata"><img src="https://agentmods.dev/badge/rules/channnnsm/cursor-dmbok/dmbok_metadata.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.00532 |
| Opus 5 | $0.00000 | $0.00266 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
dmbok_metadata 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 5d 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.
This is a copy
100% identical to dmbok_data_quality — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
メタデータ管理のDMBOKルール
このルールはデータ定義関連ファイルにおいて、DMBOKのメタデータ管理の原則に従うようAIに指示するものです。
基本原則
- データ項目には、必ずビジネス上の意味、技術的な仕様、データオーナーを明記すること
- データリネージ（データの発生源と変換経路）を可能な限り追跡・記録すること
- メタデータは一貫性と正確性を保ち、常に最新の状態を維持すること
- メタデータの標準化されたフォーマットと用語を使用すること
- メタデータの収集と管理プロセスを文書化すること
デザインガイドライン
- ビジネスメタデータと技術メタデータを明確に区別して記述すること
- データオーナーとデータスチュワードの責任範囲を明確にすること
- データの機密性レベルと保持期間を必ず指定すること
- データ品質基準と検証ルールを詳細に記述すること
- 他のデータとの関連性と依存関係を明示すること
チェックポイント
- すべてのデータ項目に適切なビジネス定義が付与されているか
- 技術仕様が明確かつ詳細に記述されているか
- データオーナーとデータスチュワードが特定されているか
- データの発生源と利用先が明記されているか
- データの品質要件と検証ルールが定義されているか
注意事項
- 抽象的な表現ではなく、具体的で明確な表現を使用すること
- 未検証または不確かな情報はメタデータとして記録しないこと
- 組織内の標準用語集と整合したメタデータを作成すること
- メタデータ自体の更新履歴を管理すること
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.
- 5d ago First seen · 40 lines · 0 tokens per session scan A 8031092d6228
dmbok_metadata is a cursor rule published in the GitHub repository channnnsm/cursor-dmbok (9 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 532 tokens. A static security scan graded it A with 0 findings. It is 100% identical to dmbok_data_quality, differing in 54 lines, and is treated as a copy.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
query-optimization
查詢優化、EXPLAIN、index 設計與 RLS 效能測量.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.