Is acm-handoff safe to install?

SaferSkills independently audited acm-handoff (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/acm-handoff/SKILL.md · 1 file

skills/acm-handoff/SKILL.md2.1 KB · Markdown

name: acm-handoff

description: Use when resuming work from a previous session that reached context threshold, or when a handoff summary exists. Reads handoff state and markdown to restore context, todos, and continue seamlessly.

Context Handoff

This skill loads handoff content from a previous session that reached the context threshold.

Instructions

When this skill is invoked:

Check for structured state at .claude/claudikins-acm/handoff-state.json
Read the handoff markdown at .claude/claudikins-acm/handoff.md
Present both to understand what was being worked on
Restore todos if active todos exist in the state
Continue the work from where it was left off

File Locations

File	Purpose
`.claude/claudikins-acm/handoff-state.json`	Structured state (preferred)
`.claude/claudikins-acm/handoff.md`	Human-readable summary

Reading the State

The structured state JSON contains:

context.current_objective - What was being worked on
context.active_todos - Pending/in-progress todos to restore
context.key_files_modified - Recently changed files
git.branch - Git branch at handoff time
git.modified_files - Uncommitted changes

After Reading

Restore todos using TodoWrite if active_todos has entries
Summarise the previous session's state for the user
Ask if they want to continue from where they left off
Clean up the handoff files after successful restoration

Cleanup

After successfully restoring context, offer to clean up:

rm -f .claude/claudikins-acm/handoff-state.json
rm -f .claude/claudikins-acm/handoff.md

If No Handoff Exists

If neither file exists, inform the user:

No handoff is currently active
A handoff is created when context usage hits the threshold (default 60%)
They can configure the threshold via /acm:config

_Claudikins Automatic Context Manager_ _To configure settings, use: /acm:config_

acm-handoff— agent skill

Is acm-handoff safe to install?

Context Handoff

Instructions

File Locations

Reading the State

After Reading

Cleanup

If No Handoff Exists

Audit the pieces. Scan the whole. Decide.