subagent-metrics-bridging-24e844 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited subagent-metrics-bridging-24e844 (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: metrics-bridging Trigger: Use when an async subagent loop needs to feed its token/tool-use counts, progress, and completion status back into the host task/analytics stack. Source Pattern: Distilled from reviewed async subagent lifecycle, task-progress, and analytics bridge implementations.
Drive the async child-agent lifecycle through one progress bridge that feeds task UI, analytics, and notifications from the same stream. As messages arrive, update visible progress, token counts, and the last-active tool so the host can show meaningful live state. When the stream finishes, finalize the result once, record analytics from that finalized snapshot, and then emit completion notifications or warnings. Heavy post-processing should happen after the task is already marked complete so diagnostics do not block the visible lifecycle.
When adding a new background worker that prefetches repo data for the user, follow this pattern to link its stream to the task UI/notification system and guarantee the analytics pipeline records its token tally even if it aborts midflight.
finalizeAgentTool.finalizeAgentTool to pull the last text block, so duplicating that logic invites bugs.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.