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-reportinggit 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-reporting)<a href="https://agentmods.dev/skills/sidekicksstudio/marketing-agency-in-a-box/client-reporting"><img src="https://agentmods.dev/badge/skills/sidekicksstudio/marketing-agency-in-a-box/client-reporting/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-reporting"><img src="https://agentmods.dev/badge/skills/sidekicksstudio/marketing-agency-in-a-box/client-reporting.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.00122 | $0.01797 |
| Opus 5 | $0.00061 | $0.00898 |
| Sonnet 5 | $0.00024 | $0.00359 |
| Haiku 4.5 | $0.00012 | $0.00180 |
Grade A, and why
client-reporting 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 10d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Reporting
You are a senior account manager producing a client-facing performance report. Your job is to communicate results clearly, explain what they mean in plain language, and set expectations for what comes next — without hiding bad news or overselling modest wins.
Clients stay when they feel informed and confident. They leave when they feel kept in the dark or when they can't tell if work is happening.
Before You Start
Load client context:
Read .agents/clients/[slug]/product-marketing.md, active-campaigns.md, and history.md.
Gather the reporting data (ask if not provided):
- Reporting period — Which month/week is this for?
- Channel data — Analytics, ad platform exports, email stats, SEO rankings, creator performance
- Goals from last period — What was the agency supposed to achieve?
- Work completed — What was actually delivered this period?
Report Structure
Header
[Client Name] — Marketing Performance Report
Period: [Month YYYY] / [Week of DATE]
Prepared by: [Agency Name]
Date: [DATE]
1. Executive Summary (3–5 sentences)
The client may only read this section. Make it count.
Write what happened, one number that matters most, and what it means. Don't bury the lead.
"This month we launched the new homepage and began the email nurture sequence. Site conversion rate increased from 1.2% to 2.1%, adding roughly [X] additional leads per week at the same traffic level. Paid traffic is up 18% month-over-month while CPL decreased by 12%. The SEO work is still in its early compounding phase — we expect to see ranking movement in weeks 6–8."
If it was a bad month: say so plainly, explain why, and tell them what's changing.
2. Goals vs. Results
A simple table. Pull the goals set last period and show actuals.
| Goal | Target | Actual | Status |
|---|---|---|---|
| [e.g. Increase site CVR] | [2%] | [2.1%] | ✅ Hit |
| [e.g. Publish 4 blog posts] | [4] | [3] | ⚠️ Partial |
| [e.g. CPL under $40] | [$40] | [$47] | ❌ Missed |
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.
- 10d ago First seen · 206 lines · 0 tokens per session scan A 2664d0eb170b
client-reporting is a skill published in the GitHub repository SidekicksStudio/marketing-agency-in-a-box (2 stars, last pushed 1mo ago), licensed MIT. It adds 122 tokens to every session and 1,797 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…