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 jeremylongworth-source/AgentSkills --skill brand-social-launch-packgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/brand-social-launch-pack)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/brand-social-launch-pack"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/brand-social-launch-pack/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/jeremylongworth-source/agentskills/brand-social-launch-pack"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/brand-social-launch-pack.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.00073 | $0.00621 |
| Opus 5.5 | $0.00029 | $0.00248 |
| Sonnet 5.5 | $0.00015 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
brand-social-launch-pack 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Social Launch Pack
Core Workflow
- Identify the launch object, audience, primary CTA, proof asset, channels, launch window, owner, review requirements, and non-goals.
- Build a message hierarchy: one-line promise, buyer or reader problem, proof, CTA, secondary resource, and objection or trust notes.
- Plan owned-profile updates only when they support the launch. Keep the main profile link focused on the highest-priority conversion path.
- Create the launch package: hero post, image or video asset brief, pinned or featured content, reply/comment follow-up, article or long-form post, and platform-specific caption variants.
- Use
owned-social-profile-auditfor profile visibility and link checks,social-asset-productionfor visual assets, andai-video-prompt-packfor AI-generated video prompt packs when those tasks are in scope. - Add a publish checklist, verification plan, and post-launch follow-up queue.
Package Patterns
For a lightweight launch, produce:
- profile link recommendation
- primary post
- one image or video prompt
- pinned or featured post recommendation
- follow-up comment or reply
- verification checklist
For a full launch, also add:
- article or long-form post
- platform-specific variants
- content calendar for the first week
- repurposed short-form hooks
- owner-side checklist for manual publishing
Freshness Rule
Before giving platform-specific rules for profile links, pinned posts, Articles, Highlights, Shorts, Reels, verification, or asset dimensions, verify current official platform documentation when practical.
Safety Rules
- Do not fabricate traction, testimonials, endorsements, usage numbers, or customer claims.
- Do not publish, pin, schedule, boost, or change profile settings unless the user explicitly asks and account access supports it.
- Include disclosure, rights, and human-review notes for sponsored, affiliate, AI-generated, or reputation-sensitive launches.
- Keep launch copy honest about alpha, beta, preview, or experimental status.
What ships with it
2 files 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 · 79 lines · 73 tokens per session scan A f0d847f88202
brand-social-launch-pack is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 73 tokens to every session and 621 once invoked, about $0.0003 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
idd-spec-audit
Semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use on request to audit .github/instructions, the issue-authoring skill bundle, and the installed agent entry files (CLAUDE.md…
unity-yaml-format
Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
authos-rbac-control
Manage AuthOS organization members, roles, invitations, SCIM tokens, and capability-based permissions. Use when implementing team administration, custom roles, service access grants, invitation flows, SCIM provisioning, or authorization checks inside an AuthOS tenant.
authos-service-management
Manage AuthOS tenant services, OAuth client credentials, redirect URIs, device activation URIs, plans, API keys, SAML settings, and checkout. Use when creating or configuring applications inside an AuthOS organization.
authos-platform-deployment
Deploy and configure an AuthOS API instance from source or Docker. Use when setting database backend, JWT signing keys, environment variables, billing provider, SMTP, GeoIP, Docker images, health checks, or production reverse proxy settings.
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.