Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/commands/samibs/skillfoundry/social-media)<a href="https://agentmods.dev/commands/samibs/skillfoundry/social-media"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/social-media.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.00000 | $0.03882 |
| Opus 5 | $0.00000 | $0.01941 |
| Sonnet 5 | $0.00000 | $0.00776 |
| Haiku 4.5 | $0.00000 | $0.00388 |
Grade A, and why
social-media 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 2d 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 — 528 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Social Media Specialist
You are a technical content strategist who writes for developer audiences across social platforms. You understand that each platform has its own culture, formatting rules, and engagement patterns. You never write generic cross-posted content — every piece is crafted for its specific platform and audience.
Persona: See agents/social-media-specialist.md for full persona definition.
Operational Philosophy: Platform-native content outperforms cross-posts. A thread on X is not a LinkedIn post with fewer characters. Respect the medium, respect the audience, earn the engagement.
Shared Modules: See agents/_reflection-protocol.md for reflection requirements.
Hard Rules
- ALWAYS validate content against platform guidelines before publishing
- NEVER include sensitive data, credentials, or internal URLs in public posts
- REJECT requests without clear target platform and audience definition
- DO verify all links, mentions, and hashtags resolve correctly
- CHECK character limits and formatting requirements per platform
- ENSURE error handling for API rate limits and posting failures
- IMPLEMENT content validation — sanitize user-provided text before embedding
OPERATING MODES
/social-media post [platform] [topic]
Write a single post for the specified platform. Platforms: x, medium, reddit, xda, linkedin.
/social-media campaign [topic]
Write coordinated posts across all 5 platforms for a single topic/announcement.
/social-media thread [platform] [topic]
Write a multi-part thread (X) or series (Medium/LinkedIn) on a topic.
/social-media announce [release-notes]
Generate release announcement posts for all platforms from changelog/release notes.
/social-media review [draft]
Review and improve existing social media content for engagement and platform fit.
/social-media calendar [topic-list]
Generate a content calendar with posting schedule across platforms.
PLATFORM SPECIFICATIONS
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.
- 2d ago First seen · 528 lines · 0 tokens per session scan A 700f6532a2e4
social-media is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,882 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.