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 agentmods add settings/jameywarren/shopify-claude-quickstart/settingsgit clone --depth 1 https://github.com/jameywarren/shopify-claude-quickstartWrote 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/settings/jameywarren/shopify-claude-quickstart/settings)<a href="https://agentmods.dev/settings/jameywarren/shopify-claude-quickstart/settings"><img src="https://agentmods.dev/badge/settings/jameywarren/shopify-claude-quickstart/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
settings 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 4d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"hooks": {
"SessionStart": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "printf 'shopify-claude-quickstart loaded.\\n\\nFirst time on this store?\\n /init-store STORE.myshopify.com - auth, theme pull, audit, fill CLAUDE.md\\n /brief-interview - fill in client-brief/ conversationally\\n /brief-quick - single-file lightweight brief\\n\\nReturning?\\n /recover-context - re-anchor on where we left off\\n\\nBuilding?\\n /brand-system /design-intake /implement-mockup-module\\n /homepage-from-brief /pdp-audit /metafield-schema /nav-build /seo-audit /alt-text ...\\n Type / to see all commands.\\n\\nReminders:\\n - Validate GraphQL with shopify-plugin:shopify-admin BEFORE executing\\n - Mutations require --allow-mutations on shopify store execute\\n - Push to a DEV theme first, never live\\n - Run /log-session before closing\\n'"
},
{
"type": "command",
"command": "mkdir -p docs && echo \"SESSION START: $(date '+%Y-%m-%d %H:%M:%S')\" >> docs/session-activity.log"
},
{
"type": "command",
"command": "REMOTE=$(git remote get-url origin 2>/dev/null || echo ''); if echo \"$REMOTE\" | grep -q 'shopify-claude-quickstart'; then git fetch origin main --quiet 2>/dev/null; BEHIND=$(git rev-list HEAD..origin/main --count 2>/dev/null || echo 0); [ \"$BEHIND\" -gt '0' ] && printf '\\n⬆ shopify-claude-quickstart has %s new commit(s) on GitHub. Run /toolkit-update to pull the latest.\\n' \"$BEHIND\" || true; fi"
}
]
}
],
"Stop": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "mkdir -p docs && echo \" $(date '+%H:%M:%S') turn\" >> docs/session-activity.log"
}
What else settings.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 4d ago First seen · 36 lines scan A 97b137149af8
settings is a settings file published in the GitHub repository jameywarren/shopify-claude-quickstart (2 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 settings, from other repositories
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
RuView
Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
orm
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.