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 skills/miyatti777/ai-plc/db-syncnpx skills add miyatti777/ai-plc --skill db-syncgit clone --depth 1 https://github.com/miyatti777/ai-plcWrote 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/skills/miyatti777/ai-plc/db-sync)<a href="https://agentmods.dev/skills/miyatti777/ai-plc/db-sync"><img src="https://agentmods.dev/badge/skills/miyatti777/ai-plc/db-sync.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.00033 | $0.00573 |
| Opus 5 | $0.00016 | $0.00287 |
| Sonnet 5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
ai-plc-db-sync 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.
What it actually says
Codex adapter: AI-PLC DB Sync
このadapterはCodex固有の入口だけを提供し、処理本文は.claude互換runtimeの正本を使う。
前提確認（変更前に必須）
repository root基準で、次の4ファイルがregular fileとして存在し読めることを確認する。
.claude/skills/ai-plc/db-sync/SKILL.md.claude/rules/ai-plc-system.md.claude/rules/ai-plc-session.md.claude/rules/ai-plc-adaptive.md
1件でも欠落・読取不能なら、DB、Wiki、外部同期先その他の状態を変更せず、欠落pathを列挙して停止する。
実行
- 必須3 Rulesを上記順で最後まで読む。
- 正本
.claude/skills/ai-plc/db-sync/SKILL.mdを最後まで読む。 - コマンド、DB、同期設定は正本に記載された
.claude/db/配下を使用する。 statusとdry-runはread-only確認として実行できる。pull、push、syncはユーザーが明示した操作範囲だけ実行する。- Claude Code固有のAgent toolまたは起動表記が現れた場合は、許可されたCodex sub-agentまたは対応する
$skill-nameへ変換する。 - 正本のClaude Code native memory参照を
~/.claudeへ解決してはならない。Codexでは読取・更新とも行わず、該当処理は変更なし — スキップ（Codex adapter: Claude native memory非対象）と記録する。
Read-only diagnostics
ユーザーがAI-PLC prerequisite diagnosticsを明示した場合は正本の同期処理を実行せず、変更0で停止する。正本Skillと必須3 Rulesの4件ごとにabsolute_path、sha256、最初のH1、末尾のversion行をprerequisite_diagnosticsとして返す。4件のいずれかが欠落・読取不能ならstatus: blockedと対象pathを返す。Rules 3件は併せてrule_diagnosticsとして識別できるようにする。
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 · 33 lines · 33 tokens per session scan A b8750aae3de4
ai-plc-db-sync is a skill published in the GitHub repository miyatti777/ai-plc (45 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 573 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-30.
Other skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
debugging
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.