background-agent-pings — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited background-agent-pings (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.
Trust system reminders as agent progress notifications. Don't poll.
When you launch a background agent, continue working on other tasks. The system will notify you via reminders when:
Agent <id> progress: X new tools used, Y new tokens1. Task(run_in_background=true, prompt="... Output to: .claude/cache/agents/<type>/output.md")
2. Continue with next task immediately
3. When system reminder shows agent activity, check if output file exists
4. Read output file only when agent signals completion# BAD: Polling wastes tokens and time
Task(run_in_background=true)
Bash("sleep 5 && ls ...") # polling
Bash("tail /tmp/claude/.../tasks/<id>.output") # polling
TaskOutput(task_id="...") # floods contextTaskOutput floods main context with full agent transcript~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.