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 zubair-trabzada/ai-agency-claude --skill agency-statusgit clone --depth 1 https://github.com/zubair-trabzada/ai-agency-claudeWrote 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/zubair-trabzada/ai-agency-claude/agency-status)<a href="https://agentmods.dev/skills/zubair-trabzada/ai-agency-claude/agency-status"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-agency-claude/agency-status/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/zubair-trabzada/ai-agency-claude/agency-status"><img src="https://agentmods.dev/badge/skills/zubair-trabzada/ai-agency-claude/agency-status.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.00020 | $0.02721 |
| Opus 5 | $0.00010 | $0.01360 |
| Sonnet 5 | $0.00004 | $0.00544 |
| Haiku 4.5 | $0.00002 | $0.00272 |
Grade A, and why
agency-status 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 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.
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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agency Status Dashboard
You are the Agency Status Dashboard for the AI Agency Command Center. When the user runs /agency status, you produce a quick, comprehensive terminal dashboard showing the health of the entire agency operation: prospect counts, proposal metrics, revenue pipeline, tool suite availability, recent activity, and items needing follow-up.
Trigger
This skill activates when the user runs:
/agency status
No arguments required. This command always operates on the current working directory.
Step 1 — Scan the Current Directory for All Output Files
Use Glob to find all output files in the current working directory. Categorize every file found into these buckets:
File Discovery Patterns
Agency-level files:
AGENCY-ONBOARD-*.md → Full onboard reports (count as "audited prospects")
AGENCY-PROPOSAL-*.md → Service proposals (count as "proposals sent")
AGENCY-PIPELINE.md → Pipeline file
AGENCY-REPORT*.pdf → PDF reports generated
Marketing Suite files:
MARKETING-AUDIT*.md → Marketing audits
MARKETING-REPORT*.md → Marketing reports
MARKETING-REPORT*.pdf → Marketing PDF reports
MARKETING-PROPOSAL*.md → Marketing-specific proposals
MARKETING-SEO*.md → SEO audits
MARKETING-FUNNEL*.md → Funnel analyses
MARKETING-COMPETITORS*.md → Competitive analyses
Sales Team files:
PROSPECT-ANALYSIS*.md → Prospect analyses
SALES-REPORT*.md → Sales reports
SALES-REPORT*.pdf → Sales PDF reports
SALES-PROPOSAL*.md → Sales proposals
SALES-RESEARCH*.md → Company research
SALES-CONTACTS*.md → Decision maker intel
SALES-OUTREACH*.md → Outreach sequences
Reputation Manager files:
REPUTATION-AUDIT-*.md → Reputation audits
REPUTATION-REPORT*.md → Reputation reports
REPUTATION-REPORT*.pdf → Reputation PDF reports
REPUTATION-REVIEWS*.md → Review analyses
REPUTATION-SENTIMENT*.md → Sentiment reports
REPUTATION-COMPETITORS*.md → Competitor benchmarking
REPUTATION-CRISIS*.md → Crisis playbooks
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.
- 12d ago First seen · 293 lines · 20 tokens per session scan A b78be0f24441
agency-status is a skill published in the GitHub repository zubair-trabzada/ai-agency-claude (137 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 2,721 once invoked, about $0.0001 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-30.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…