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/pedrogiudice/lex-vector/settingsgit clone --depth 1 https://github.com/PedroGiudice/lex-vectorGrade A, and why
lex-vector 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 yesterday.
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.
This is a copy
84% identical to scalar — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"enabledPlugins": {
"feature-dev@claude-code-plugins": true,
"agent-sdk-dev@claude-code-plugins": true,
"vercel@claude-plugins-official": true,
"context7@claude-plugins-official": true,
"frontend-design@claude-plugins-official": true,
"serena@claude-plugins-official": true,
"atlassian@claude-plugins-official": true,
"ralph-wiggum@claude-plugins-official": true,
"feature-dev@claude-plugins-official": true,
"code-review@claude-plugins-official": true,
"commit-commands@claude-plugins-official": true,
"pr-review-toolkit@claude-plugins-official": true,
"linear@claude-plugins-official": true,
"hookify@claude-plugins-official": false,
"stj-vec-tools@opc-plugins": true
},
"outputStyle": "Technical Director"
}
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.
- yesterday First seen · 21 lines scan A 5b8759c51c27
lex-vector is a settings file published in the GitHub repository PedroGiudice/lex-vector (5 stars, last pushed 3mo 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. It is 84% identical to scalar, differing in 20 lines, and is treated as a copy.
Other settings, from other repositories
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.
electron
Agent settings declaring 17 allowed tools.
uv
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
ui-ux-pro-max-skill
Agent settings declaring 7 allowed tools.