Packet FactorySAFE
A framework-agnostic, git-native standard for defining AI agents
Overview
A framework-agnostic, git-native standard for defining AI agents
799d6d0ad18cOBSERVED · 2026-10-07What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: packet-factory version: 1.0.0 description: > Creates, reviews, and dispatches atomic work packets. Every task with a side effect requires an APPROVED packet before execution. Scope is immutable after approval — expansion requires a new packet. --- # Packet Factory The packet factory is the gatekeeper between intent and execution. Nothing with a side effect runs without an APPROVED packet. ## Commands ```bash # Create a new packet (DRAFT status) skills/packet-factory/new-packet.sh \ --intent "Post daily update to Slack #arc-angels" \ --source "Ludo DM 2026-04-01 09:00" \ --destination "Slack #arc-angels" # Review a packet (set APPROVED or REJECTED) skills/packet-factory/review-packet.sh --id 2026-04-01-001 # Dispatch an APPROVED packet (executes and logs output) skills/packet-factory/dispatch-packet.sh --id 2026-04-01-001 ``` ## Packet Queue All in-flight packets live in `memory/packet-queue.md`. The heartbeat pre-flight check reads this file. DRAFT packets older than 24h are escalated to Ludo. ## Scope Lock Rule Once a packet is APPROVED, `scope_locked_at` is set and the scope field is frozen. If the task grows (new deliverable discovered, Ludo asks for something extra), the current packet is dispatched as-is and a **new packet** is created for the expansion. Never mutate an approved packet's intent or output. This prevents the single most common failure mode: scope creep → context balloon → session death.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
799d6d0ad18cfull audit observations/trust-audit/skill/open-gitagent__packet-factory.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 799d6d0ad18c | SAFE | B | 89 | first audit |
Questions
What does the Packet Factory skill do?
A framework-agnostic, git-native standard for defining AI agents
Is Packet Factory safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Packet Factory access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (799d6d0ad18c), read on 2026-10-07. The repository is watched, and a new audit runs when it changes — this is the first audit.