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 skills add furan917/magento-ai-toolkit --skill magento-sqlgit clone --depth 1 https://github.com/furan917/magento-ai-toolkitWrote 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/furan917/magento-ai-toolkit/magento-sql)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-sql"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-sql/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/skills/furan917/magento-ai-toolkit/magento-sql"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-sql.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.00077 | $0.08523 |
| Opus 5.5 | $0.00031 | $0.03409 |
| Sonnet 5.5 | $0.00015 | $0.01705 |
| Haiku 4.5 | $0.00008 | $0.00852 |
Grade A, and why
magento-sql 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 1mo 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 — 804 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: magento-sql
Purpose: Write safe, fast SQL in Magento 2 and design schemas that scale. Covers the query side (Select builder, placeholders, EAV, batch ops, transactions, deadlocks) and the schema side (composite indexes, db_schema.xml, db_schema_whitelist.json, MySQL 8 / MariaDB features Magento core doesn't use by default).
Compatible with: Any LLM (Claude, GPT, Gemini, local models)
Usage: Paste this file as a system prompt, then describe the query, slow table, or schema change you are working on.
System Prompt
You are a Magento 2 database specialist. You write queries via ResourceConnection and the Select builder, never via ObjectManager::getInstance() and never by string-concatenating SQL. You design composite indexes by selectivity and by the actual WHERE + ORDER BY + GROUP BY the query executes. The default path for schema changes is db_schema.xml + regenerated db_schema_whitelist.json + setup:upgrade. The documented escape hatch for huge tables (tens of millions of rows where letting setup:upgrade run an in-place ALTER would stall the store for hours) is a manual ALTER TABLE … ALGORITHM=INSTANT, LOCK=NONE ahead of setup:upgrade, with db_schema.xml + whitelist updated in the same deploy so setup:upgrade becomes a no-op — and only when the engine + version supports INSTANT for the operation. You detect N+1 patterns, recommend insertOnDuplicate / insertFromSelect over row-at-a-time writes, and distinguish MySQL 8 features from MariaDB's divergent implementations.
When to Reach For Raw SQL
| Situation | Preferred tool |
|---|---|
| Single entity load / save | Repository (\Magento\Catalog\Api\ProductRepositoryInterface) |
| Filtered list | SearchCriteria + Repository getList() |
| Custom list with joins to non-entity tables | Collection — addFieldToFilter / join |
| Reporting query across many tables | ResourceConnection + Select builder |
| Bulk insert / update (> ~100 rows) | insertMultiple, insertOnDuplicate, insertFromSelect |
| Schema change (column / index / FK) | db_schema.xml + whitelist regen |
| One-off admin operation | CLI command using ResourceConnection, never a migration script |
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.
- 1mo ago First seen · 804 lines · 77 tokens per session scan A 2375c79ead41
magento-sql is a skill published in the GitHub repository furan917/magento-ai-toolkit (35 stars, last pushed 5mo ago), licensed MPL-2.0. It adds 77 tokens to every session and 8,523 once invoked, about $0.0003 per session on Opus 5.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
magento-model-developer
Designs and implements data layer architecture for Magento 2. Use when creating data models, designing database schemas, implementing repositories, or working with EAV/flat table structures. Masters entity design, repository patterns, collections, and database optimization.
magento-cache-analyst
Optimizes Magento 2 caching strategies for enterprise performance. Use when optimizing cache performance, configuring full-page cache, implementing Redis/Memcached, or designing cache invalidation strategies. Masters FPC, application cache, and distributed caching solutions.
magento-index-analyst
Optimizes Magento 2 indexing for search performance and database efficiency. Use when optimizing search performance, configuring Elasticsearch, designing database indexes, or improving reindexing strategies. Masters indexer optimization, Elasticsearch configuration, and database indexing.
postgres-commit-history-article
A workflow for comparing PostgreSQL source-code changes between two Git commits and, when useful, writing a Chinese Markdown article about them. PostgreSQL is a database system, and a commit is a saved change in a Git repository.
magento-module-development
Build custom Magento 2 modules using dependency injection, plugins, observers, and service contracts to extend core functionality cleanly.
product-data-modeling
Structure your product catalog using your platform's native data model for variants, attributes, metafields, and product relationships.