allow-cmd-recent

A command for reviewing recent Bash commands and identifying ones that could be added to an allowed-command list.

In plain words
What is it for?
Use it to review recent Bash tool calls and find possible whitelist candidates.
Why use it?
It helps inspect recent command use when deciding which shell operations should be trusted.

Command for Claude Code

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 commands/connorads/dotfiles/allow-cmd-recent
Clone the repo
git clone --depth 1 https://github.com/connorads/dotfiles

Made for: Claude Code.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 581 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 3 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00581
Opus 5 $0.00004 $0.00291
Sonnet 5 $0.00002 $0.00116
Haiku 4.5 $0.00001 $0.00058

Measured yesterday against content hash bb2e0f5b6535, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

allow-cmd-recent scanned grade D with 3 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

Add qualifying commands to the bash permissions "allow" list in ~/.claude/settings.json under `.permissions.allow`.

Recursive force deletehighDestructive command

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

- **Destructive operations**: rm -rf, git reset --hard, git checkout -- (file), git clean

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **Arbitrary curl/wget**: curl to arbitrary URLs could fetch and pipe malicious scripts. Only allow specific safe patterns (curl -I, curl -s -o /dev/null -w)
.claude/commands/allow-cmd-recent.md · 44 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 · 44 lines · 8 tokens per session scan D bb2e0f5b6535

Subscribe to this mod's changes

allow-cmd-recent is a command published in the GitHub repository connorads/dotfiles (16 stars, last pushed yesterday), with no licence file. It adds 8 tokens to every session and 581 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 3 findings (reads agent configuration directories, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.