agent-startup-and-context-ingestion — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited agent-startup-and-context-ingestion (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.
How an agent becomes useful after launch: AGENTS.md overlays, role files, skills, rig specs, workflow specs, startup checklists, refocus messages, and any future "rig context" command or skill-librarian surface.
It is the current concrete startup path inside the broader context-engineering-and-retrieval primitive. Startup gets a seat into the right initial shape; context engineering is the larger question of how a seat gets the right context for the work it is doing right now.
Most coordination failures are not tool failures; they are context failures. Agents need to know their role, operating mode, coordination convention, boundaries, and current product intent. If startup context is scattered or stale, agents execute the wrong thing very efficiently.
claude-compaction-restoreStartup proof should:
When a seat's startup is artifact-backed mental-model rebuild (active-work reentry case, distinct from reusable Agent Starters / priming packs):
The primary surfaces a startup ingestion path reads:
Authority-rank + read-vs-write posture governs which surfaces a startup-ingestion path can write vs only read; treat overlays as write-restricted unless your role explicitly authors them.
Per agent-startup-guide.md (product reference doc) and the team handbook:
| Startup files | Skills |
|---|---|
| Rig-specific, role-specific identity | Reusable SOPs / methodology / knowledge |
| Tell agent WHO it is, WHAT it's working on, HOW this team operates | Tell agent HOW to do something (transferable across rigs) |
Examples: role.md, CULTURE.md, startup/context.md | Examples: openrig-user, test-driven-development, dogfood |
| Authored per-rig | Authored once, used everywhere |
Don't put skill content in startup files. Don't put identity content in skills. The 7-layer additive startup model (agent / profile / rig / culture / pod / member / operator) handles the layering.
forming-an-openrig-mental-model skill — orientation for new agentsclaude-compaction-restore skill — restore-time startup ingestion after compactionseat-continuity-and-handover skill — packet shape that survives seat resets~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.