ttl-429 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ttl-429 (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
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.
Run from the project root:
node .skills/ttl-429/scripts/ttl_429.mjs [--ttl-sec N] <instance.ARM.ndjson> [more.ndjson ...]clawback's keep-alive ping re-reads the cached prefix, so a successful ping (200, cache_read>0) demonstrably refreshes Anthropic's TTL. The open question is the 429'd ping: Anthropic returns no usage body, so we cannot see whether the request still touched the cache. The only observable is the next success on the same SESSION KEY.
For each 429'd ping it finds the next 200-with-usage on that session and asks: did more than --ttl-sec elapse since the last known-warm event (so the cache should have expired), with no intervening success to refresh it? If yes and the probe still reads warm → REFRESH (the 429'd ping kept it alive). If the probe reads cold → NO-REFRESH. If the boundary was never crossed, or a 200 landed first, → INCONCLUSIVE.
A paired run where the cache is allowed to go cold across the TTL boundary with only a 429'd ping spanning it. That means:
--inject-extended-cache-ttl);
the isolation);
Without 429'd pings the analyzer says so plainly — the stock cadence keeps the cache warm, so no ping is ever isolated across a boundary.
The per-session warmth table flags any session with ≥3 pings and zero warm pings as ⚠ PHANTOM: an uncacheable aux context (sub-1024-token prefix) the keep-alive armed and is pinging for pure cost. Cross-check against the keepAliveMinPrefixBytes gate in src/keepalive.js.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.