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/report-shopify-app)<a href="https://agentmods.dev/commands/khadinakbarlabs/shopify-app-builder/report-shopify-app"><img src="https://agentmods.dev/badge/commands/khadinakbarlabs/shopify-app-builder/report-shopify-app/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/report-shopify-app"><img src="https://agentmods.dev/badge/commands/khadinakbarlabs/shopify-app-builder/report-shopify-app.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.00013 | $0.00139 |
| Opus 5.5 | $0.00005 | $0.00056 |
| Sonnet 5.5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
report-shopify-app 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.
What it actually says
report-shopify-app
Skills: shopify-project-copilot, app-release-readiness
Read the listed skills. Validate the selected project's record and generate its local reports with the contained helper. Don't infer readiness from counts or label recorded claims independently verified. Keep local, dev-store, production and review evidence separate. Open the actual report through the host preview when supported; otherwise return Markdown. Do not publish a report, fetch private analytics, run app code or create tracking. With no state/files, provide a clearly unsaved report and offer optional local initialization.
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 · 11 lines · 13 tokens per session scan A 5ceda3507c64
report-shopify-app is a command published in the GitHub repository khadinakbarlabs/shopify-app-builder (2 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 139 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-10-05.
Other commands, from other repositories
feedback
Review comments on your display.dev artifacts, then apply them, reply, and resolve the threads after you approve.
help
A help command that displays the ocul-pm reference card and recommends the next suitable step. ocul-pm is a project-tracking setup for coding agents that uses journals, plans, tools, skills, and hooks.
next
A command that takes the next unfinished leaf item from an active project plan and runs one implementation cycle. The cycle includes implementation, verification, journal entry, and plan-status update.
project_init
A command that starts tracking a project with ocul-pm by creating its project records and agent logging rules.
standup
A command that creates a daily stand-up report from an ocul-pm project's work logs and plan. A stand-up is a short update on completed work, blocked work, and next steps.
status
Display project status, active tracks, and next actions.