SKILL verified MIT Self-run

Press1 Check

Name: Press1 Check
Availability: InStock
Author: christophecapel

skill-christophecapel-claude-mechanisms-tools-press1-check · by christophecapel

Audit which Bash commands required manual approval ("press 1") in Claude Code sessions. Use when the user says "press1-check", "press 1 check", "permission audit", or wants to review which commands need allow-listing.

↗ Website ↗ Repository

— No reviews yet

0 installs

3 views

0.0% view→install

Install

$ agentstack add skill-christophecapel-claude-mechanisms-tools-press1-check

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

✓ Prompt-injection patterns
✓ Secret / credential exfiltration
✓ Dangerous shell & filesystem operations
✓ Untrusted network calls
✓ Known-malicious package signatures

What it can access

✓ Network access No
✓ Filesystem access No
✓ Shell / process execution No
✓ Environment & secrets No
✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Press1 Check? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.

About

/press1-check -- Permission Audit

Audit which Bash commands triggered manual approval prompts in Claude Code sessions.

How it runs

Two paths:

Manual: type /press1-check to force a re-audit. Default mode is since the last run (state-tracked at ~/.claude/state/press1-check.json), so the typical run only surfaces new ground.
Auto (optional): the script supports --auto-stop-hook mode designed to be wired as a Claude Code Stop hook. State at ~/.claude/state/press1-check.json. 6-hour cooldown bounds compute. When LOW-risk additions are found, a one-shot summary at ~/.claude/hooks-state/press1-check-pending.json surfaces in the next session-start priority snapshot. See README for setup.

Usage

/press1-check -- since the last run (default, state-tracked)
/press1-check --days N -- last N days across all project dirs
/press1-check --latest-session -- only the single most recent session
/press1-check --all-recent -- all sessions from the last 24h
/press1-check --since YYYY-MM-DD -- all sessions since a date
/press1-check -- specific session

Steps

Run: python3 audit-permissions.py with any arguments the user provided. Default audits since ~/.claude/state/press1-check.json#last_run_ts (bootstraps to last 3 days when state is missing, e.g. on a new machine).
Display the output to the user exactly as printed (it includes color-coded risk levels).
If LOW-risk suggestions appear, add them to ~/.claude/settings.json (read-only commands are safe). Skip env-var-prefix suggestions like Bash(WT=*) -- they don't generalize because the actual command follows the assignment.
Do NOT auto-add MEDIUM or HIGH risk commands without explicit approval.
After editing ~/.claude/settings.json, re-run the audit and report before/after counts so the user can see the coverage delta.
Each successful interactive run updates the state file -- the next run is automatically scoped to "since now."

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Author: christophecapel
Source: christophecapel/claude-mechanisms-tools
License: MIT
Homepage: https://github.com/christophecapel/claude-mechanisms

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

v0.1.0 Imported from the upstream source.