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 m3taz-ahmed/ai-globals --skill personal-brandinggit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/personal-branding)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/personal-branding"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/personal-branding/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/m3taz-ahmed/ai-globals/personal-branding"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/personal-branding.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.00032 | $0.00590 |
| Opus 5 | $0.00016 | $0.00295 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
personal-branding 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 9d 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.
What it actually says
[SKILL] personal-branding [OBJ] Build a durable personal brand that compounds trust and inbound demand. Define positioning, produce pillar content, and show up consistently across X, YouTube, blog, and speaking.
[RULES]
- [REQ] Positioning first: one sentence — "I help achieve via ." Everything else ladders to it. Cross-link
freelance-nichefor ICP + niche. - [REQ] Pillar content: pick 3 themes you want to be known for; publish weekly on at least two (X threads + long-form blog/YouTube). Repurpose via
content-marketing. - [REQ] Voice guide: define tone (formal/casual), banned words, signature sign-off. Store in
brand-kitfor reuse. - [CMD] Context7 IDs:
gitroomhq/postiz-app(distribution),plausible/analytics(reach),umami-software/umami(engagement). - [REQ] Free-first channels: X (organic), YouTube (free), dev.to/Medium (free), LinkedIn (via
linkedin-platform). Paid boosting only as parity. - [REQ] Consistency system: batch-create, schedule via Postiz, review weekly. A 12-week streak beats sporadic spikes.
- [REQ] Proof engine: every claim backed by a case study, metric, or public artifact. Builds E-E-A-T (see
seo-lord). - [REQ] Arabic/RTL: if audience is Arabic, run a mirrored Arabic brand stream (separate or bilingual posts); RTL typesetting per
arabic-freelance. - [REQ] Authority ladder: post → thread → talk → guest article → podcast → book/course. Move up as proof accumulates.
- [REQ] Measurement: track follower quality (not just count), profile-visit→DM rate, inbound lead count. Feed to
marketing-analytics.
[PROHIBIT]
- No fabricated authority claims or fake results.
- No buying followers/engagement.
- No brand voice that contradicts
brand-kit. - No Arabic stream with broken RTL/typesetting.
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.
- 9d ago First seen · 40 lines · 32 tokens per session scan A 4297d822d6bc
personal-branding is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 590 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-09-03.
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…