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 sugarforever/01coder-agent-skills --skill promote-postgit clone --depth 1 https://github.com/sugarforever/01coder-agent-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/sugarforever/01coder-agent-skills/promote-post)<a href="https://agentmods.dev/skills/sugarforever/01coder-agent-skills/promote-post"><img src="https://agentmods.dev/badge/skills/sugarforever/01coder-agent-skills/promote-post.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.01432 |
| Opus 5 | $0.00046 | $0.00716 |
| Sonnet 5 | $0.00018 | $0.00286 |
| Haiku 4.5 | $0.00009 | $0.00143 |
Grade A, and why
promote-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 8d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Promote Post
Write a promotional tweet for a published article. The tweet is a teaser — it opens the story, not summarizes it.
Core Philosophy
The article is a block of cheese. The tweet is also part of that same cheese — not a label on the packaging, not a description on the shelf. It's the first bite.
The tweet and the article should feel like one continuous piece. When a reader goes from the tweet to the article, the transition should be seamless — as if they were already inside the story and simply kept reading. There is no "In this article I talk about..." because that language creates a boundary between the tweet and the content. The tweet IS the content. It just happens to be the part that lives on the timeline.
A summary tells readers what the article says so they don't have to click. The tweet we want makes readers feel like the story has already started, and the link is where it continues. The reader should feel pulled forward, not informed.
Workflow
Step 1: Get the Article
The user provides a URL (Substack, X Article, blog post, or any published link).
- Use WebFetch (with
r.jina.aiprefix if needed) to retrieve the full content - Read carefully — understand the narrative arc, not just the key points
- Identify: What's the emotional core? What's the tension? What's the surprise or insight that makes this worth reading?
If the user provides a file path instead:
- Use Read to load the content
- Ask for the published URL to include in the tweet
Step 2: Find the Hook
Look for one of these angles in the article:
- A tension or contradiction — something that creates curiosity ("X should work, but it doesn't. Here's why...")
- A vivid scene or moment — drop the reader into the middle of a situation
- A surprising fact or framing — something that makes you go "wait, really?"
- A relatable feeling — something the audience has experienced but hasn't articulated
- A question the reader didn't know they had — then imply the article answers it
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.
- 8d ago First seen · 141 lines · 91 tokens per session scan A 2a6b841d131e
promote-post is a skill published in the GitHub repository sugarforever/01coder-agent-skills (134 stars, last pushed 2mo ago), licensed MIT. It adds 91 tokens to every session and 1,432 once invoked, about $0.0005 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…