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/boussadjra/vuestrata/settingsgit clone --depth 1 https://github.com/boussadjra/vuestrataWrote 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/boussadjra/vuestrata/settings)<a href="https://agentmods.dev/settings/boussadjra/vuestrata/settings"><img src="https://agentmods.dev/badge/settings/boussadjra/vuestrata/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
vuestrata 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-settings.json",
"permissions": {
"allow": [
"Bash(vp check)",
"Bash(vpr lint)",
"Bash(vpr fmt --check)",
"Bash(vpr test --run)",
"Bash(vpr test:unit)",
"Bash(vpr test:component)",
"Bash(vpr test:integration)",
"Bash(vpr typecheck)",
"Bash(vpr typecheck:e2e)",
"Bash(vp exec vue-tsc --noEmit)",
"Bash(vpr gen --help)",
"Bash(vp toolchain)",
"Bash(node scripts/lint/run-custom-rules.mjs)",
"Bash(node scripts/docs/check-links.mjs)",
"Bash(node scripts/docs/check-links.mjs --quiet)",
"Bash(node scripts/msw/check-worker-version.mjs)",
"Bash(node scripts/build/verify-bundle.mjs *)",
"Bash(git status *)",
"Bash(git diff *)",
"Bash(git log *)",
"Bash(git branch *)",
"Bash(git show *)"
]
},
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "vp check",
"timeout": 180,
"statusMessage": "Running vp check"
}
]
}
]
}
}
What else settings.json configures
This page is one entry in a file that holds 2. 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 · 44 lines scan A 9fb39b1c88b9
vuestrata is a settings file published in the GitHub repository boussadjra/vuestrata (111 stars, last pushed 10d 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-30.
Other settings, from other repositories
melta-ui
Agent settings declaring 1 hook event (PostToolUse).
nextjs-template-mongodb
Agent settings configuring enabledPlugins.
cloudflare-workers-react-boilerplate
Agent settings declaring 41 allowed tools.
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).