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 caravanglory/magehub --skill module-setupgit clone --depth 1 https://github.com/caravanglory/magehubWrote 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/caravanglory/magehub/module-setup)<a href="https://agentmods.dev/skills/caravanglory/magehub/module-setup"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/module-setup/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/caravanglory/magehub/module-setup"><img src="https://agentmods.dev/badge/skills/caravanglory/magehub/module-setup.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.00028 | $0.02753 |
| Opus 5.5 | $0.00011 | $0.01101 |
| Sonnet 5.5 | $0.00006 | $0.00551 |
| Haiku 4.5 | $0.00003 | $0.00275 |
Grade A, and why
module-setup 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 2mo 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Scripts
Activation
Use When
- The task is to create or modify Magento declarative schema, data patches, schema patches, db_schema_whitelist.json, or setup-time data migrations.
- The task mentions db_schema.xml, DataPatchInterface, SchemaPatchInterface, patch_list, setup:upgrade, or schema whitelist generation.
Do Not Use When
- The task is runtime repository CRUD with no schema or setup-time data change.
- The task asks for legacy InstallSchema/UpgradeSchema for a new Magento 2.3+ module.
Required Inputs
- Table/column/index/constraint definitions or data migration intent, existing data safety requirements, and target module name.
- Whether setup:upgrade and whitelist generation can run in the current environment.
Workflow
- Inspect existing schema, patches, resource models, setup history, and data ownership before changing database structure.
- Represent standard DDL in db_schema.xml; use schema patches only for operations declarative schema cannot express.
- Make data patches idempotent and dependency-ordered with getDependencies() and getAliases() where needed.
- Regenerate db_schema_whitelist.json after schema changes and verify setup status.
Guardrails
- Do not drop, rename, or narrow columns with existing data without an explicit migration plan and approval. (approval required)
- Do not hand-edit db_schema_whitelist.json except to review generated output.
- Ask before running setup:upgrade because it can apply database changes. (approval required)
Verification
- Run XML validation or bin/magento setup:db:status after schema changes.
- Run bin/magento setup:db-declaration:generate-whitelist --module-name=Vendor_Module after db_schema.xml changes.
- Run setup:upgrade in an approved local/staging environment and report whether data patches executed cleanly.
Output Contract
- List schema objects changed, patch classes added, idempotency checks, whitelist changes, and database commands run.
- Flag any data-loss or rollback risk explicitly.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 329 lines · 28 tokens per session scan A 6fa9b49c9014
module-setup is a skill published in the GitHub repository caravanglory/magehub (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 2,753 once invoked, about $0.0001 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-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
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.
atlas-mssql
SQL Server specifics for Atlas (also Azure SQL and MSSQL): login, dev database and URL scope (mode=schema vs mode=database, the database query parameter), compatibility level and collation, system-generated constraint names, clustered index defaults and datetime2 precision in HCL, GO batches and the delimiter…
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…
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.
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.