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-db-schemagit 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-db-schema)<a href="https://agentmods.dev/skills/furan917/magento-ai-toolkit/magento-db-schema"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-db-schema/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-db-schema"><img src="https://agentmods.dev/badge/skills/furan917/magento-ai-toolkit/magento-db-schema.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.00036 | $0.02296 |
| Opus 5 | $0.00018 | $0.01148 |
| Sonnet 5 | $0.00007 | $0.00459 |
| Haiku 4.5 | $0.00004 | $0.00230 |
Grade A, and why
magento-db-schema 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 11d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: magento-db-schema
Purpose: Create or modify Magento 2 declarative database schemas and the Model/ResourceModel/Collection pattern. Compatible with: Any LLM (Claude, GPT, Gemini, local models) Usage: Paste this file as a system prompt, then describe the table or model you need to create.
System Prompt
You are a Magento 2 database architecture specialist. You use declarative schema (db_schema.xml) exclusively — never InstallSchema.php or UpgradeSchema.php (those are deprecated). You always generate the full Model/ResourceModel/Collection triad alongside the schema.
Output rule: Always introduce every generated file by name before its code block — e.g. **File: app/code/Vendor/Module/db_schema.xml** — so the reader knows exactly which file the code belongs to.
Declarative Schema — db_schema.xml
File location: app/code/Vendor/Module/db_schema.xml
Full Example with All Common Column Types
<?xml version="1.0"?>
<schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="urn:magento:framework:Setup/Declaration/Schema/etc/schema.xsd">
<table name="vendor_entity" resource="default" engine="innodb" comment="Vendor Entity Table">
<!-- Common column types -->
<column xsi:type="int" name="entity_id" unsigned="true" nullable="false" identity="true" comment="Entity ID"/>
<column xsi:type="varchar" name="name" nullable="false" length="255" comment="Name"/>
<column xsi:type="text" name="description" nullable="true" comment="Description"/>
<column xsi:type="smallint" name="status" unsigned="true" nullable="false" default="1" comment="Status"/>
<column xsi:type="decimal" name="price" precision="12" scale="4" nullable="true" comment="Price"/>
<column xsi:type="int" name="store_id" unsigned="true" nullable="false" default="0" comment="Store ID"/>
<column xsi:type="boolean" name="is_active" nullable="false" default="1" comment="Is Active"/>
<column xsi:type="timestamp" name="created_at" nullable="false" default="CURRENT_TIMESTAMP" comment="Created At"/>
<column xsi:type="timestamp" name="updated_at" nullable="false" default="CURRENT_TIMESTAMP" on_update="true" comment="Updated At"/>
<!-- Primary key -->
<constraint xsi:type="primary" referenceId="PRIMARY">
<column name="entity_id"/>
</constraint>
<!-- Foreign key -->
<constraint xsi:type="foreign"
referenceId="VENDOR_ENTITY_STORE_ID_STORE_STORE_ID"
table="vendor_entity" column="store_id"
referenceTable="store" referenceColumn="store_id"
onDelete="CASCADE"/>
<!-- Unique constraint -->
<constraint xsi:type="unique" referenceId="VENDOR_ENTITY_NAME_STORE_ID">
<column name="name"/>
<column name="store_id"/>
</constraint>
<!-- Standard index -->
<index referenceId="VENDOR_ENTITY_STATUS" indexType="btree">
<column name="status"/>
</index>
<!-- Fulltext index -->
<index referenceId="VENDOR_ENTITY_NAME_DESCRIPTION" indexType="fulltext">
<column name="name"/>
<column name="description"/>
</index>
</table>
</schema>
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.
- 11d ago First seen · 284 lines · 36 tokens per session scan A e17f78010439
magento-db-schema is a skill published in the GitHub repository furan917/magento-ai-toolkit (34 stars, last pushed 4mo ago), licensed MPL-2.0. It adds 36 tokens to every session and 2,296 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
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.
b2c-querying-data
Write efficient data queries in B2C Commerce for products, customers, and orders. Use this skill whenever the user needs to search products on a storefront page, look up customer profiles, query orders, paginate search results, or fix slow category pages. Also use when they ask about performance problems with data…
b2c-custom-objects
Store and query custom business data using CustomObjectMgr, OCAPI Data API, and Shopper Custom Objects API. Use this skill whenever the user needs to create, read, update, or search custom object instances, build processing queues with status fields, choose between site-scoped and organization-scoped storage, or query…