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 BayramAnnakov/ai-personal-os-skills --skill linkedin-research-postgit clone --depth 1 https://github.com/BayramAnnakov/ai-personal-os-skillsWrote 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/bayramannakov/ai-personal-os-skills/linkedin-research-post)<a href="https://agentmods.dev/skills/bayramannakov/ai-personal-os-skills/linkedin-research-post"><img src="https://agentmods.dev/badge/skills/bayramannakov/ai-personal-os-skills/linkedin-research-post/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/bayramannakov/ai-personal-os-skills/linkedin-research-post"><img src="https://agentmods.dev/badge/skills/bayramannakov/ai-personal-os-skills/linkedin-research-post.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.00069 | $0.02250 |
| Opus 5 | $0.00034 | $0.01125 |
| Sonnet 5 | $0.00014 | $0.00450 |
| Haiku 4.5 | $0.00007 | $0.00225 |
Grade A, and why
linkedin-research-post 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Research Post
You help the user research a topic and publish a LinkedIn post backed by multi-source research. The full pipeline: Research -> Analyze -> Draft -> Review -> Publish.
Prerequisites - VERIFY BEFORE STARTING
Before launching any agents, run these checks:
1. AnySite MCP canary check:
Call mcp__anysite-mcp__duckduckgo_search with query "test" and count 1. If it returns results, AnySite is connected. If it errors, tell the user:
- Claude Desktop: Customize > Connectors > AnySite > Connect
- CLI:
claude mcp add anysite -s user -- npx -y @anthropic/anysite-mcp - Signup: anysite.io - promo code BAYRAMMCP for 30 days free
DO NOT launch research agents until this check passes.
2. Voice profile: Check for voice/style in this order:
SOUL.mdin project root or home directoryuser-profile.mdin project root- Memory files via recall
- If nothing found, ask the user: "How would you describe your writing style in 1 sentence?"
3. Unipile MCP (optional - check only at publish time):
- Signup: unipile.com - 7-day free trial, no credit card required
- Config:
claude mcp add-json unipile '{"type":"http","url":"https://developer.unipile.com/mcp","headers":{"X-API-KEY":"YOUR_API_KEY"}}'
Workflow
Step 1: Get the Topic
If the topic was provided via $ARGUMENTS, use it directly.
Otherwise ask: "What topic should your LinkedIn post be about?"
If too broad, narrow it:
- "What specific angle or insight do you want to share?"
- "Who is your audience on LinkedIn?"
Step 2: Research (2-3 min)
Launch 3 parallel sub-agents. Each agent prompt MUST include the exact MCP tool names below. Do NOT say "use AnySite MCP" - agents don't know what that means.
CRITICAL: Include these exact instructions in each agent prompt:
Sub-agent 1 - LinkedIn perspective:
Research "[TOPIC]" on LinkedIn.
You MUST use these exact MCP tools (not WebSearch, not WebFetch):
- mcp__anysite-mcp__search_linkedin_posts(keywords="[TOPIC]", count=10, date_posted="past-week")
- mcp__anysite-mcp__get_linkedin_post_comments(urn="[post_urn]", count=5) for top posts
Find the 5 most engaged posts. For each note:
- Author name and headline
- Post text (first 200 chars)
- Reaction count and comment count
- The angle/take they used
Summarize: what angles get traction, what's overdone, what's missing.
PRIORITY: Try mcp__anysite-mcp tools first. If they fail, fall back to WebSearch/WebFetch.
At the end of your report, note which tools you actually used (MCP vs fallback).
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 · 213 lines · 69 tokens per session scan A 5efb64750e75
linkedin-research-post is a skill published in the GitHub repository BayramAnnakov/ai-personal-os-skills (20 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 2,250 once invoked, about $0.0003 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…