agentmods.dev

loki-mode

A settings file that defines four events in the coding agent’s lifecycle: when a session starts, before and after a tool call, and when the agent stops.

In plain words
What is it for?
It is for configuring the hooks used by the loki-mode setup.
Why use it?
It gives the project a defined place to connect automated actions to these agent events.

Settings file for Claude Code

1.1k +2 yesterday A scan tokens not measured no licence
View the source file asklokesh/loki-mode
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/asklokesh/loki-mode/settings
Clone the repo
git clone --depth 1 https://github.com/asklokesh/loki-mode

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 unknown No closer match found in the catalogue.
Security

Grade A, and why

loki-mode 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 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.

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 · 49 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 · 49 lines scan A d0c33cea26e3

Subscribe to this mod's changes

loki-mode is a settings file published in the GitHub repository asklokesh/loki-mode (1,054 stars, last pushed yesterday), 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 A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Autonomousai-agentsaideranthropicclaude
Related

Other settings, from other repositories

loupe

Agent settings declaring 1 allowed tools.

StephanSchmidt/loupe · not measured

forgecraft-mcp

MCP configuration declaring 2 servers: forgecraft, context7.

jghiringhelli/forgecraft-mcp · not measured

supabase

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

supabase/supabase · not measured

superset

Agent settings declaring 1 hook event (PreToolUse).

apache/superset · 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