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 floomhq/moto --skill linkedin-copygit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/linkedin-copy)<a href="https://agentmods.dev/skills/floomhq/moto/linkedin-copy"><img src="https://agentmods.dev/badge/skills/floomhq/moto/linkedin-copy.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.00072 | $0.00884 |
| Opus 5 | $0.00036 | $0.00442 |
| Sonnet 5 | $0.00014 | $0.00177 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
linkedin-copy 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 7d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LinkedIn Copy Skill
The Problem with Most LinkedIn Content
LinkedIn is saturated with:
- Humble brags disguised as lessons ("I was rejected 47 times before...")
- Fake vulnerability ("I almost quit until...")
- Generic advice ("5 things I wish I knew earlier")
- Engagement bait ("Comment YES if you agree")
Good LinkedIn content is rare precisely because it's genuinely useful, honest, and specific.
What Works
Specificity over generality: "We increased checkout conversion by 23% by removing one field" beats "small changes = big results"
Show the work: What actually happened, what you built, what you learned. Data > inspiration.
Honest takes: Disagree with conventional wisdom if you have evidence. Nuance beats hot takes.
Short paragraphs: One idea per paragraph. No walls of text. LinkedIn is a scroll feed.
Post Formats
The Observation Post
Share something you noticed that others might have missed.
[Specific observation about your field/work]
[Why this matters - the implication]
[Your take or what you're doing about it]
The Build Post
Show something you built, shipped, or created.
[What you built - one sentence]
[Why it was hard / what problem it solves]
[Key result or learning]
[Link or call to action if relevant]
The Learning Post
Share something you learned that changed how you think.
[The old assumption you had]
[What changed your mind - specific incident, data, or experience]
[The new way you think about it]
The Contrarian Take
Disagree with conventional wisdom, backed by evidence.
[The common advice / conventional wisdom]
[Why it's wrong or incomplete - with your evidence]
[What you think instead]
Formatting Rules
- First line is the hook - must make someone stop scrolling
- Short paragraphs - 1-3 sentences max
- No bullet lists on first post (LinkedIn de-ranks heavy formatting)
- End with a question only if you genuinely want answers (not engagement bait)
- No hashtag spam - 2-3 relevant hashtags maximum, at the end
- No "thoughts?" at the end - it's a tell that the post is engagement farming
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.
- 7d ago First seen · 122 lines · 72 tokens per session scan A 027d61f5c3ee
linkedin-copy is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 884 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-08-30.
Other skills, from other repositories
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-foundation-core
Provides MoAI-ADK foundational principles including TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, agent catalog reference, and token budget management (absorbed from moai-foundation-context). Use when referencing TRUST 5 gates, SPEC workflow, or context window…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…