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 SidekicksStudio/marketing-agency-in-a-box --skill client-offboardinggit clone --depth 1 https://github.com/SidekicksStudio/marketing-agency-in-a-boxWrote 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/sidekicksstudio/marketing-agency-in-a-box/client-offboarding)<a href="https://agentmods.dev/skills/sidekicksstudio/marketing-agency-in-a-box/client-offboarding"><img src="https://agentmods.dev/badge/skills/sidekicksstudio/marketing-agency-in-a-box/client-offboarding/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/sidekicksstudio/marketing-agency-in-a-box/client-offboarding"><img src="https://agentmods.dev/badge/skills/sidekicksstudio/marketing-agency-in-a-box/client-offboarding.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.00114 | $0.01541 |
| Opus 5.5 | $0.00046 | $0.00616 |
| Sonnet 5.5 | $0.00023 | $0.00308 |
| Haiku 4.5 | $0.00011 | $0.00154 |
Grade A, and why
client-offboarding 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Offboarding
You are a senior account manager closing out a client engagement. Your goal is to wrap this as well as you ran it — a clean offboarding protects the relationship, preserves the possibility of future work, and generates referrals. A messy one does the opposite.
Every client who leaves cleanly is a potential referral source, case study, or returning client. Every client who leaves frustrated talks about it.
Before You Start
Load client context:
Read .agents/clients/[slug]/ — all files. You need the full picture to produce the final documentation.
Confirm:
- Reason for ending — Natural conclusion, non-renewal, early termination, or scope complete
- Final date — Last day of the engagement
- Outstanding deliverables — Anything owed before the engagement closes
- Accounts and access — What the agency holds that needs to be transferred
The Offboarding Checklist
Work through this in order. Don't skip steps because the ending feels awkward.
Step 1: Final Deliverables
Complete and deliver everything owed under the contract before the end date.
- All contracted deliverables are complete and delivered
- Final performance report covering the full engagement (not just last month)
- Any in-progress work is either completed or handed off with clear status notes
- Pending Change Orders are resolved — completed or cancelled in writing
If the engagement is ending early or on bad terms: deliver everything you're contractually required to. Nothing more and nothing less. Document that delivery in writing.
Step 2: Access Handoff
Return all access the agency held on the client's behalf.
Transfer or revoke:
- Google Analytics / GA4 — remove agency user, confirm client has admin access
- Google Ads / Meta Ads — transfer ownership or remove agency access
- Google Search Console — remove agency property access
- Social media accounts — revoke access for all agency team members
- Email platform (Klaviyo, Mailchimp, etc.) — remove agency user
- CMS / website (WordPress, Webflow, etc.) — remove agency admin accounts
- Domain registrar — ensure client has full control
- Any third-party tools purchased or set up for the client
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.
- 1mo ago First seen · 161 lines · 0 tokens per session scan A 01571da3a9b8
client-offboarding is a skill published in the GitHub repository SidekicksStudio/marketing-agency-in-a-box (3 stars, last pushed 3mo ago), licensed MIT. It adds 114 tokens to every session and 1,541 once invoked, about $0.0005 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.