exact-rendered-decision-journaling-91fb2e — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited exact-rendered-decision-journaling-91fb2e (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.
Domain: tool-orchestration Trigger: Apply whenever per-message budgeting rewrites tool_result content so transcripts capture the preview string and resume logic can reapply the same decisions. Source Pattern: Distilled from reviewed tool-loop and result-shaping patterns.
After enforceToolResultBudget persists a candidate, produce a ToolResultReplacementRecord (kind: 'tool-result', toolUseId, replacement) that stores the literal preview returned by buildLargeToolResultMessage. Pass newlyReplaced to the writeToTranscript callback so every replacement is serialized in the conversation transcript; later, reconstructContentReplacementState(messages, records, inheritedReplacements) can rebuild the same seenIds/replacements map, and provisionContentReplacementState gates the feature flag (tengu_hawthorn_steeple) so journaling stays optional.
toolUseId with each record so resume enforcement can quickly look up replacements without re-running persistence.parentState.replacements into reconstructForSubagentResume when resuming forks so inherited decisions reapply exactly.writeToTranscript; it may be undefined in ephemeral contexts, so only call it when provided.provisionContentReplacementState should return undefined and journaling remains inert.In the query loop pass the transcript writer to applyToolResultBudget; the callback serializes newlyReplaced records, which are later replayed by provisionContentReplacementState(initialMessages, records) during resume so the budget enforces the same replacements it originally made.
persistToolResult succeeds and the preview is built—the replacement string must exist before you write it down.kind: 'tool-result' or the toolUseId fields; reconstructContentReplacementState relies on them to filter and lookup.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.