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/marcozorn/agencykit/client-reportnpx skills add MarcoZorn/agencykit --skill client-reportgit clone --depth 1 https://github.com/MarcoZorn/agencykitWrote 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/marcozorn/agencykit/client-report)<a href="https://agentmods.dev/skills/marcozorn/agencykit/client-report"><img src="https://agentmods.dev/badge/skills/marcozorn/agencykit/client-report.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.1 | $0.00038 | $0.02312 |
| Opus 5 | $0.00019 | $0.01156 |
| Sonnet 5 | $0.00008 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
client-report 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 5d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Report
When to use this skill
English: "monthly report", "performance report", "send report to client", "campaign results", "wrap up the month".
Italiano: "report mensile", "resoconto", "risultati campagna", "report cliente", "chiudi il mese".
What this skill does
Turns a pile of numbers into a report a client actually reads and trusts. It leads with a plain-language summary, names the three things that worked with real figures, is honest about what did not and what you are doing about it, sets three priorities for next month, and backs it all with one clean data table showing month-over-month deltas. The tone is confident and clear — not defensive, not a data dump.
Inputs required
- Client name and the reporting period (e.g. March 2026).
- The channels in scope (Instagram, TikTok, Meta Ads, email, Google Ads, web).
- This period's numbers and last period's numbers for each KPI. If last period is missing, mark deltas
n/a — first report. - The goal the client cares about (the KPI from the brief).
- Anything notable — a launch, a budget change, an outage, a viral post. Context that explains the numbers.
If numbers are missing, ask for them. Do not fabricate metrics — a made-up figure in a client report is the fastest way to lose the account.
Output format
- EXECUTIVE SUMMARY — three sentences, no jargon.
- WHAT WORKED — top 3 results, each with a number.
- WHAT DIDN'T — honest, solution-focused, never defensive.
- NEXT MONTH — three priorities.
- THE NUMBERS — a table: channel / KPI / this period / last period / delta.
- CLOSING LINE — one branded, forward-looking sentence.
Brand voice
If a BRAND.md file exists in this skill's folder (.claude/skills/client-report/BRAND.md) or in .claude/brand/BRAND.md (global fallback), read it before generating output and apply its tone, terminology, and examples to all text you produce. A skill-local BRAND.md overrides the global one; if neither exists, use a clean, professional default voice.
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.
- 5d ago First seen · 186 lines · 38 tokens per session scan A 1e5cc3d785ab
client-report is a skill published in the GitHub repository MarcoZorn/agencykit (6 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 2,312 once invoked, about $0.0002 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
status-card-query
Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.
silicon-steward
人类供奉调度官，把人类该提供之资源、反馈与执行动作压成清单与协议.
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
memory-continuity
Preserves cross-session continuity with deterministic MEMORY.md, index.md, and snapshot handoffs under .agentic/memories/.
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
git-worktree-workspaces
Sets up and uses Git worktrees for parallel task workspaces in the same repository clone, including safe cleanup of local worktrees. Invoked when the user asks to work on multiple branches at once, isolate tasks without extra clones, or create/remove worktrees.