agentmods.dev

settings

A settings file that lists five tools the coding agent is allowed to use.

In plain words
What is it for?
Use it to configure or review the tools available to an agent.
Why use it?
It makes the agent’s tool access explicit and limited. This helps control which actions the agent can take.

Settings file for Claude Code

2 3d ago C scan tokens not measured no licence
View the source file outputty/claude-plugin
Install

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.

agentmods
npx agentmods add settings/outputty/claude-plugin/settings
Clone the repo
git clone --depth 1 https://github.com/outputty/claude-plugin

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan C 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Security

Grade C, and why

settings scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"ask": ["Bash(rm -rf:*)", "Bash(git clean -f:*)"]
.claude/settings.json · 31 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 31 lines scan C a3ba5252a9e5

Subscribe to this mod's changes

settings is a settings file published in the GitHub repository outputty/claude-plugin (2 stars, last pushed 3d ago), with no licence file. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review
Related

Other settings, from other repositories

supabase

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

supabase/supabase · not measured

claude-cookbooks

Agent settings declaring 2 hook events (SessionStart, PreToolUse).

anthropics/claude-cookbooks · not measured

claude-code-best-practice

Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.

shanraisshan/claude-code-best-practice · not measured

electron

Agent settings declaring 17 allowed tools.

electron/electron · not measured

uv

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

astral-sh/uv · not measured

ui-ux-pro-max-skill

Agent settings declaring 7 allowed tools.

nextlevelbuilder/ui-ux-pro-max-skill · not measured