agentmods.dev

ai-cli-utils

Agent settings that enable experimental agent teams and allow Python, package, Git, and GitHub commands.

In plain words
What is it for?
They are for projects that need Python tooling, dependency management, version control, and GitHub operations.
Why use it?
They define a limited set of command-line tools the agent can use for development work.

Settings file for Claude Code

2 yesterday A scan tokens not measured original MIT
View the source file sergeiwallace/ai-cli-utils
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/sergeiwallace/ai-cli-utils/settings
Clone the repo
git clone --depth 1 https://github.com/sergeiwallace/ai-cli-utils

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 A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

ai-cli-utils 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.

.claude/settings.json · 15 lines

What it actually says

{
  "env": {
    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
  },
  "permissions": {
    "allow": [
      "Bash(python:*)",
      "Bash(pip:*)",
      "Bash(uv:*)",
      "Bash(git:*)",
      "Bash(gh:*)"
    ]
  }
}
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 · 15 lines scan A 088bb568ecd0

Subscribe to this mod's changes

ai-cli-utils is a settings file published in the GitHub repository sergeiwallace/ai-cli-utils (2 stars, last pushed yesterday), 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.

Backend and APIsGit and workflowLanguagesai-toolsclaude-codeclideveloper-toolsmoshpython
Related

Other settings, from other repositories

agentic-context-engine

Agent settings declaring 2 allowed tools.

kayba-ai/agentic-context-engine · not measured

cortex-mcp

Agent settings declaring 13 allowed tools.

turfptax/cortex-mcp · not measured

Hades

Agent settings declaring 5 allowed tools.

TheArcForge/Hades · not measured

Dense-Evolution

NISQ Quantum Simulation toolkit- JAX-Native.

tatopenn-cell/Dense-Evolution · not measured

settings

Agent settings declaring 4 hook events (SessionStart, PreToolUse, PostToolUse, PostToolUseFailure).

TechHU-GS/cc-discipline · not measured

supabase

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

supabase/supabase · not measured