handoff-intent — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited handoff-intent (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.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<what-to-do>
Load the active intent. If PATHMODE_API_KEY is set, call get_current_intent (Pathmode MCP). Otherwise read intent.md from the project root.
Summarize the session in four buckets:
For each decision and discovery, call log_implementation_note with a self-contained summary. Assume the next reader has none of this conversation's context.
If outcomes are delivered, propose calling update_intent_status with shipped. If the spec needs amendments based on what was learned, propose them.
</what-to-do>
<supporting-info>
Bad: "Fixed the timeout bug."
Good: "Reduced payment timeout from 30s to 3s by switching from polling to webhook callbacks. Webhook requires Stripe whitelist for the staging IP — see ticket OPS-1234 for the IP request. Tradeoff accepted: webhooks are async, so the success page now needs to handle the pending state for ~2s while waiting for confirmation."
The "why" and the "what's still implicit" are the parts that disappear if you don't capture them.
shipped — code is merged AND the outcome is observable in productionverified — the outcome metric has held for at least one full cycle (e.g., one week, one release)Do NOT bump to shipped if outcomes are only partially delivered. Either leave the status and log the partial delivery as a note, or propose a spec amendment that scopes the outcome to what was actually shipped.
A commit message records what the code did. A handoff note records what the engineer learned and decided.
Both matter. They live in different places. This skill writes to the intent layer; git keeps the code layer.
Routine implementation details ("used a for loop instead of map") are not handoff material. Capture only what would surprise the next reader — non-obvious decisions, hidden constraints, accepted tradeoffs.
</supporting-info>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.