keystone-reload-notice — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited keystone-reload-notice (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.
Tell the user the current session's ambient context is stale.
Guides under .keystone/harness/guides/ are loaded at session start by the agent runtime (via the menu file overlay or an equivalent mechanism). When the audit or learn flow modifies a guide, the current session keeps reading the pre-edit body until it reloads. This skill emits the explicit reload notice.
guides/ file was created, edited, archived, or moved.reorders.
during the session.
Harness reload needed ────────────────────── The following guides were updated this session:
The current agent context is stale until the menu file is refreshed. Re-run keystone_target_add(<agent>, force=True) (or reload your IDE / agent session) before the next task.
keystone_target_add(agent, force=True) torefresh the overlay block in the menu file. This still leaves the in-memory agent context stale; only a fresh session fully picks up the change.
A reload notice (free-form text). No file writes by default; the user decides when to reload.
restarts, the in-memory context lags.
an earlier one, surface each subsequent guide change.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.