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.
git clone --depth 1 https://github.com/khadinakbarlabs/shopify-app-builderWrote 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/commands/khadinakbarlabs/shopify-app-builder/audit-scopes)<a href="https://agentmods.dev/commands/khadinakbarlabs/shopify-app-builder/audit-scopes"><img src="https://agentmods.dev/badge/commands/khadinakbarlabs/shopify-app-builder/audit-scopes/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/commands/khadinakbarlabs/shopify-app-builder/audit-scopes"><img src="https://agentmods.dev/badge/commands/khadinakbarlabs/shopify-app-builder/audit-scopes.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.00020 | $0.00588 |
| Opus 5 | $0.00010 | $0.00294 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
audit-scopes 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 8d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit and Minimize API Scopes
You are reviewing and optimizing Shopify API scopes to follow least-privilege principle and prepare for App Store certification.
Scope Inventory and Assessment
-
List current scopes
- Extract scopes from shopify.app.toml SCOPES array
- Common scopes: read_products, write_orders, read_customers, read_inventory, manage_apps
- Document each scope's purpose in app (e.g., read_products → product sync feature)
- Reference skill: scope reference (02_apis.md)
-
Analyze scope usage
- Search codebase for GraphQL mutations using each scope
- Identify read vs write scope requirements per feature
- Check if any scopes unused or can be removed
- Example: if no customer mutations, remove write_customers scope
- Reference skill: API access patterns (02_apis.md)
-
Map scopes to features
- Create inventory: scope → feature functionality
- Identify scopes only needed for admin dashboards (can be feature-gated)
- Mark scopes needed for webhooks vs direct API calls
- Document which scopes trigger App Store review flags
- Reference skill: permission design (04_functions_auth_billing_mcp.md)
Optimization and Verification
-
Remove unnecessary scopes
- Test app functionality with minimal scope set
- Remove read scopes if information retrieved from webhooks instead
- Replace write scopes with read-only if mutations not needed
- Example: use read_orders + ORDERS_PAID webhook instead of write_orders
- Reference skill: scope minimization (02_apis.md)
-
Verify scope permissions
- Confirm each scope matches actual API calls in codebase
- Check GraphQL queries/mutations require all declared scopes
- Test app reinstall with new scope set (triggers re-authorization)
- Verify no "access denied" errors in production logs
- Reference skill: error handling (02_apis.md)
-
Document scope justification
- Create SCOPE_JUSTIFICATION.md with one-line purpose per scope
- Example: "read_products: Display product inventory levels in app dashboard"
- Include in App Store submission materials for Built for Shopify certification
- Reference skill: App Store submission (05_appstore_strategy.md)
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.
- 8d ago First seen · 64 lines · 20 tokens per session scan A d71fb6217378
audit-scopes is a command published in the GitHub repository khadinakbarlabs/shopify-app-builder (1 stars, last pushed 29d ago), licensed MIT. It adds 20 tokens to every session and 588 once invoked, about $0.0001 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-31.
Other commands, from other repositories
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
tray-referencia-api
Referência rápida de todos os endpoints da API da Tray, aceita nome do recurso como filtro.
sm-search
Ad-hoc semantic search over the supamem dual-memory collection.
project_init
A command that starts tracking a project with ocul-pm by creating its project records and agent logging rules.
analysis-next
Advance the current analysis to the next ALIVE stage.