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 skills add jqaisystems/jqai-ai-skills --skill client-delivery-auditorgit clone --depth 1 https://github.com/jqaisystems/jqai-ai-skillsWrote 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/jqaisystems/jqai-ai-skills/client-delivery-auditor)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/client-delivery-auditor"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/client-delivery-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/client-delivery-auditor"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/client-delivery-auditor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00085 | $0.00693 |
| Opus 5.5 | $0.00034 | $0.00277 |
| Sonnet 5.5 | $0.00017 | $0.00139 |
| Haiku 4.5 | $0.00009 | $0.00069 |
Grade A, and why
client-delivery-auditor 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Delivery Auditor
Turn completed project work into a checked delivery package with clear status, instructions, and communication.
1. Reconstruct the agreed delivery scope
- Confirm the project root, delivery milestone, recipient, and intended delivery channel.
- Read the latest brief, proposal, feedback, approval notes, and existing handoff material.
- Use the latest explicit decision when it changes earlier scope.
- Do not infer pricing, rights, approval, deadlines, or included deliverables.
- Preserve exact project names, links, dates, formats, and file requirements supplied by the user.
2. Audit every promised item
Classify each deliverable as:
present and verified: exists, opens correctly, and matches the agreed formatpresent but unverified: exists but still needs an appropriate checkpartial: identifiable work remainsmissing: promised but not foundexcluded: explicitly removed from scopeawaiting client: depends on approval, content, access, or another client action
Check filenames, formats, dimensions, variants, links, versions, accessibility needs, and usage instructions relevant to the project. Do not report the delivery as ready while required items are missing or unverified.
3. Prepare the handoff
- Use assets/client-delivery-handoff-template.md.
- Follow an existing delivery structure when one is already established.
- Include only final or intentionally shared files in the client package.
- Exclude scratch work, backups, raw prompts, logs, databases, account exports, and internal notes.
- Do not delete, rename, archive, upload, or change access permissions unless requested.
- Keep client-facing instructions separate from internal continuation notes.
4. Draft the delivery message
- Include
To:only when the recipient is known and always includeSubject:. - Lead with what is complete and where the client can access it.
- Keep the message concise, warm, and easy to act on.
- State missing or follow-up items plainly.
- Offer future support as an option, not a sales push.
- Request portfolio permission only when useful and include a clear opt-out.
- Never send the message or record it as sent.
What ships with it
2 files 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.
- 1mo ago First seen · 62 lines · 85 tokens per session scan A 1ef8e0919f79
client-delivery-auditor is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 85 tokens to every session and 693 once invoked, about $0.0003 per session on Opus 5.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
ledger-tasks-yylo
Retrieve any YYLO Ledger Record by ID, discover PDRs and artifacts, and manage tasks and dependencies. Use for unknown record types, universal get/search, task operations, and source-of-truth boundaries.
grill-me
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code. Use when the user wants to clarify requirements, stress-test an idea, compare approaches, or plan before coding.
wiki-yylo
Use YYLO Ledger wiki Records as durable project knowledge. Search before creating, classify information correctly, and make revision-safe Markdown updates without editing Ledger storage directly.
plan-ledger-tasks-yylo
Create a concise Product Development Requirement and one or more implementation-sized YYLO Ledger tasks when the user explicitly asks to plan or register work.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…