agentmods.dev

agami-core

Agent settings that define 26 tools the agent is allowed to use.

In plain words
What is it for?
They are for configuring which tools the agami-core agent may use.
Why use it?
They restrict the agent to an explicitly listed set of tools, making its available actions clear.

Settings file for Claude Code

29 3d ago B scan tokens not measured no licence
View the source file AgamiAI/agami-core
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/agamiai/agami-core/settings
Clone the repo
git clone --depth 1 https://github.com/AgamiAI/agami-core

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 B 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Security

Grade B, and why

agami-core scanned grade B 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 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

"Bash(chmod 755 ~/agami-artifacts)",
.claude/settings.json · 45 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. 2d ago First seen · 45 lines scan B fcd6d5413056

Subscribe to this mod's changes

agami-core is a settings file published in the GitHub repository AgamiAI/agami-core (29 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 B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metricsbusiness-intelligenceclaude-skillscontext-layercontext-layer-for-aimcp
Related

Other settings, from other repositories

lightdash

Agent settings configuring permissions.

lightdash/lightdash · not measured

honeydew-ai-coding-agents-plugins

Agent settings configuring attribution, enabledPlugins.

honeydew-ai/honeydew-ai-coding-agents-plugins · not measured

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