Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/bankszach/document-systems/verify-document-packetnpx skills add bankszach/document-systems --skill verify-document-packetgit clone --depth 1 https://github.com/bankszach/document-systemsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/bankszach/document-systems/verify-document-packet)<a href="https://agentmods.dev/skills/bankszach/document-systems/verify-document-packet"><img src="https://agentmods.dev/badge/skills/bankszach/document-systems/verify-document-packet.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00068 | $0.00364 |
| Opus 5 | $0.00034 | $0.00182 |
| Sonnet 5 | $0.00014 | $0.00073 |
| Haiku 4.5 | $0.00007 | $0.00036 |
Grade A, and why
verify-document-packet scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Verify Document Packet
Verify internal packet consistency with the deterministic MCP. Treat a valid packet as integrity evidence, never as source truth, persistence proof, human acceptance, or execution authority.
Workflow
- Confirm the input is a FULL packet containing
packet_id,expression_envelope,validation_receipt,view, andrelease_gate. - Supply only lineage envelopes actually available to the caller.
- Call
verify_document_packet. - Stop if
validis false. Report every machine reason without repairing the packet in place. - If the packet is valid, report the current receipt identity and restate its explicit non-findings.
- Create a new Expression and packet for any revision; never overwrite the historical packet while retaining its old identity.
Boundaries
- A valid content address proves supplied bytes agree, not that a server stored them durably.
- Recomputed assertion conformance proves agreement with caller-reviewed invariants, not independent source verification.
- A ready release gate means ready for a human decision, not approved, accepted, operative, deployed, or executed.
- Do not retrieve missing packets, lineage, or sources by guessing a location.
Output contract
Return packet ID, computed digest, validity, reason codes, current validation receipt ID, supplied-lineage scope, and the exact states still not established.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 39 lines · 68 tokens per session scan A e94c28248606
verify-document-packet is a skill published in the GitHub repository bankszach/document-systems (0 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 364 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ssotize
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts…
visual-html-renderer
HTMLを最終成果物として生成・検証・プレビューしたい時に使う共通レンダラー。Use this shared renderer when the user wants content turned into a final, validated, previewable HTML artifact. 現行rendererの表現能力を前提にagentが文書モデルを直接設計し、表・リスト・コード・注記・図・生成画像を選んだHTML bundleとセッション限定のプレビューURLを提示する。Triggers: html出力して, HTMLにして, HTMLで出して, この内容をHTMLで出して, HTMLでプレビューして…
image-companion
A symbolic slide image for a document passage, consistent with the artifact's companion images. Use when the user wants a diagram or visual symbol for a section. Composes /forge + Codex.
docs-sync-internal
Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…
ce:compound
Document a recently solved problem to compound your team's knowledge.
onboarding
Generate or regenerate ONBOARDING.md to help new contributors understand a codebase. Use when the user asks to 'create onboarding docs', 'generate ONBOARDING.md', 'document this project for new developers', 'write onboarding documentation', 'vonboard', 'vonboarding', 'prepare this repo for a new contributor', 'refresh…