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/rejifald/stitchapi/settingsgit clone --depth 1 https://github.com/rejifald/StitchAPIGrade A, and why
StitchAPI 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 2d 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
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"worktree": {
"baseRef": "fresh"
},
"hooks": {
"PostToolUse": [
{
"matcher": "EnterWorktree",
"hooks": [
{
"type": "command",
"statusMessage": "Installing workspace deps in worktree (pnpm install)…",
"timeout": 300,
"command": "wt=\"$(jq -r '.tool_response.path // .tool_response.worktreePath // .tool_response.cwd // .worktree_path // .cwd // empty' 2>/dev/null)\"; [ -n \"$wt\" ] || wt=\"$PWD\"; root=\"$(git -C \"$wt\" rev-parse --show-toplevel 2>/dev/null)\" || exit 0; case \"$root\" in */.claude/worktrees/*) : ;; *) exit 0 ;; esac; [ -f \"$root/pnpm-workspace.yaml\" ] || exit 0; [ -d \"$root/node_modules/.pnpm\" ] && exit 0; cd \"$root\" && pnpm install --frozen-lockfile --prefer-offline >/dev/null"
}
]
}
]
}
}
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.
- 2d ago First seen · 22 lines scan A 994e81565542
StitchAPI is a settings file published in the GitHub repository rejifald/StitchAPI (17 stars, last pushed 4d ago), licensed Apache-2.0. 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-30.
Other settings, from other repositories
huly-mcp
Agent settings declaring 1 hook event (PreToolUse).
motormetrics
Agent settings declaring 1 hook event (SessionStart).
dataflowr-tools
Agent settings declaring 1 allowed tools.
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.