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 boshi-xixixi/TraeSkill --skill linkedin-post-formattergit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/linkedin-post-formatter)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/linkedin-post-formatter"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/linkedin-post-formatter/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/boshi-xixixi/traeskill/linkedin-post-formatter"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/linkedin-post-formatter.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.00072 | $0.01488 |
| Opus 5 | $0.00036 | $0.00744 |
| Sonnet 5 | $0.00014 | $0.00298 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
linkedin-post-formatter 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Post Formatter
Transform raw content, ideas, or technical material into polished, engagement-optimized LinkedIn posts using Unicode typography and proven structural patterns.
Overview
LinkedIn only supports plain text — no Markdown rendering, no rich formatting. This skill uses Unicode Mathematical Alphanumeric Symbols to simulate bold, italic, and bold-italic text that renders natively in the LinkedIn editor without any external tools.
Unicode Typography Reference
When converting plain text into Unicode-styled LinkedIn text, first load and use references/unicode-charmap.md as the authoritative character mapping reference.
Apply these character mappings to create visual emphasis in plain text:
Bold (Mathematical Sans-Serif Bold)
Use bold for key phrases, section headers, and emphasis words.
| Plain | Unicode Bold |
|---|---|
| A-Z | 𝗔-𝗭 |
| a-z | 𝗮-𝘇 |
| 0-9 | 𝟬-𝟵 |
Italic (Mathematical Sans-Serif Italic)
Use italic for subtle emphasis, technical terms, or quotes.
| Plain | Unicode Italic |
|---|---|
| A-Z | 𝘈-𝘡 |
| a-z | 𝘢-𝘻 |
Bold-Italic (Mathematical Sans-Serif Bold Italic)
Use sparingly for maximum emphasis.
| Plain | Unicode Bold-Italic |
|---|---|
| A-Z | 𝘼-𝙕 |
| a-z | 𝙖-𝙯 |
Visual Separators
Use these characters to create visual structure:
- Section divider:
━━━━━━━━━━━━━━━━━━━━━━(box-drawing heavy horizontal) - Bullet points:
◈(diamond with dot) or◎(bullseye) - Arrow flow:
↓for vertical flow,→for horizontal continuation - Sub-points:
↳for indented sub-items - Numbered items: Use bold Unicode digits
𝟭. 𝟮. 𝟯.etc.
Post Structure Patterns
Pattern 1: Hook → Content → CTA (General Purpose)
[Bold hook line — provocative statement or question]
[1-2 lines of context setting the stage]
━━━━━━━━━━━━━━━━━━━━━━
[Main content with bold section headers]
[Bullet points using ◈ or numbered with bold digits]
━━━━━━━━━━━━━━━━━━━━━━
[Bold takeaway or summary]
[Call to action — repost, comment, or grab resource]
#Hashtags
What ships with it
1 file 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.
- 9d ago First seen · 172 lines · 72 tokens per session scan A 10fbdf86b0e0
linkedin-post-formatter is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 1,488 once invoked, about $0.0004 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
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.