agency-client-handoff

agency-client-handoff is a skill for Claude Code from PicsArt/gen-ai-skills. It costs 16 tokens per session (2,327 once invoked), scanned C, original, MIT.

A package that delivers the files and information a client needs to continue using and reproducing completed creative work.

In plain words
What is it for?
Formal handoffs to an in-house team, a new agency, or a digital asset library, including completed campaigns and contract-required source delivery.
Why use it?
When an agency hands over a project, important assets, prompts, model settings, and usage-rights records can otherwise be scattered or missing.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/extract-prompts.js "$HANDOFF/source/" > "$HANDOFF/prompts/prompt-library.json".

Part of the picsart plugin — 23 skills, 2 MCP servers shipped together

Good fit Formal handoffs to an in-house team, a new agency, or a digital asset library, including completed campaigns and contract-required source delivery.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/PicsArt/gen-ai-skills
agentmods
npx agentmods add skills/picsart/gen-ai-skills/agency-client-handoff

Made for: Claude Code.

Or install picsart, the plugin that ships this one along with the rest of its 23 skills, 2 MCP servers.

Wrote 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.

agentmods badge for agency-client-handoff

README.md
[![agentmods](https://agentmods.dev/badge/skills/picsart/gen-ai-skills/agency-client-handoff/github.svg)](https://agentmods.dev/skills/picsart/gen-ai-skills/agency-client-handoff)
Your own site
<a href="https://agentmods.dev/skills/picsart/gen-ai-skills/agency-client-handoff"><img src="https://agentmods.dev/badge/skills/picsart/gen-ai-skills/agency-client-handoff/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.

agentmods 80×15 button for agency-client-handoff

Your own site · 80×15
<a href="https://agentmods.dev/skills/picsart/gen-ai-skills/agency-client-handoff"><img src="https://agentmods.dev/badge/skills/picsart/gen-ai-skills/agency-client-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,327 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.02327
Opus 5 $0.00008 $0.01163
Sonnet 5 $0.00003 $0.00465
Haiku 4.5 $0.00002 $0.00233

Measured 12d ago against content hash 28e4334e2dd9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

agency-client-handoff scanned grade C with 2 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 12d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

1. Install CLI: curl -fsSL https://picsart.com/gen-ai-cli/install.sh | bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

1. Install CLI: curl -fsSL https://picsart.com/gen-ai-cli/install.sh | bash
skills/agency-client-handoff/SKILL.md · 192 lines

How it starts

The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agency client handoff

Package a completed engagement for transfer to the client's in-house team, DAM, or next agency — with the asset set, prompt library, model pins, rights documentation, and everything else the receiving team needs to regenerate consistent work without you in the loop.

Engagement done → reproducible handoff bundle. Knowledge transfer over lock-in: the receiving team should be able to keep the brand on-model without calling the agency back.

When to Use

  • End of an engagement, client taking work in-house
  • Transition to a new agency of record — outgoing handoff
  • Completed pitch / campaign — asset package with provenance for the client's DAM
  • Contract-mandated "source file" delivery with regeneration rights
  • Year-end portfolio snapshot for a long-term retainer client

Do not use for work-in-progress reviews (use Drive links), approvals (use proof PDFs), or internal archival (use your agency's backup). Handoff is the formal, client-owned, reproducible bundle.

Prerequisites

Ask the user (one message):

  1. Client slug + engagement scope — which client, which project or retainer period is being handed off
  2. Receiving team — in-house creative? Another agency? Which format and tools do they use (Figma, Adobe, CapCut, Notion)?
  3. Rights status — are all inputs licensed? Any stock, fonts, or reference faces that need redacting or citing?
  4. Regeneration expectation — does the client need to re-generate assets on their own, or is this a static archive?
  5. Confidentiality — any internal prompts, competitor references, or tagged metadata that must be stripped before delivery?
  6. Delivery format — zip + Drive link? Direct to client S3 / DAM? Physical drive?

If the client needs regeneration capability, they'll need the gen-ai CLI themselves — add an install guide to the bundle.

How to Run

1. INVENTORY   → pull every asset + results.json from clients/<slug>/ across the engagement
2. FILTER      → exclude drafts, rejected variants, internal-only WIP
3. STRIP       → white-label: remove agency tags, internal prompt notes, competitor refs
4. PIN MODELS  → lock every prompt's model to an exact ID + version (not "latest")
5. DOCUMENT    → generate README, RIGHTS.md, CHANGELOG, prompt library
6. PACKAGE     → zip with consistent folder structure + naming
7. VERIFY      → extract and cold-test: can a fresh machine regenerate one asset?
8. DELIVER     → upload to client destination, share link, brief the receiving team

Read the full file on GitHub · 192 lines

Changes

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.

  1. 12d ago First seen · 192 lines · 16 tokens per session scan C 28e4334e2dd9

Subscribe to this mod's changes

agency-client-handoff is a skill published in the GitHub repository PicsArt/gen-ai-skills (4 stars, last pushed 15d ago), licensed MIT. It adds 16 tokens to every session and 2,327 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

compact-manual

Claude Code skill for deterministic context compaction. Compresses the current Claude Code session to the clipboard for a manual rewind+paste workflow. A deterministic alternative to /compact that extracts literal dialog and truncates only tool outputs — no LLM summarization. Use when the user says 'compact the…

mario-hernandez/claude-compact-manual · 81 tokens

musicbrainz

Interroge l'API publique MusicBrainz pour récupérer des métadonnées musicales fiables : recherche d'artistes, discographies complètes (release-groups : albums, EPs, singles, lives, compilations), détails de releases (labels, formats, dates, pays), recordings, œuvres, relations entre entités (membres de groupe…

SteveGrosbois/tidal-cli · 177 tokens

lastfm

Access Last.fm listening history, music stats, and discovery. Query recent tracks, top artists/albums/tracks, loved tracks, similar artists, and global charts.

SteveGrosbois/tidal-cli · 36 tokens

tidal-playlist

Manage Tidal playlists — list, create, rename, delete, set public/private visibility, add or remove albums and tracks, and list tracks in a playlist. Use when the user wants to work with playlists or share one.

SteveGrosbois/tidal-cli · 50 tokens

metalorgie-weekly-releases

Récupère et filtre les sorties d'albums de la semaine publiées sur metalorgie.com ("Les sorties de la semaine"). Affiche les albums correspondant aux genres favoris de l'utilisateur (Metalcore, Post Hardcore, Hardcore, Neo metal) ainsi que les albums de groupes reconnus/notables, même hors genres favoris. Utilise ce…

SteveGrosbois/tidal-cli · 115 tokens

tidal-library

Add or remove artists, albums, or tracks from your Tidal favorites library. Use when the user wants to save music, like a song, follow an artist, or remove items from their library.

SteveGrosbois/tidal-cli · 44 tokens