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 shennawardana23/skillme --skill content-enginegit clone --depth 1 https://github.com/shennawardana23/skillmeWrote 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/shennawardana23/skillme/content-engine)<a href="https://agentmods.dev/skills/shennawardana23/skillme/content-engine"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/content-engine/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/shennawardana23/skillme/content-engine"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/content-engine.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.00078 | $0.01216 |
| Opus 5 | $0.00039 | $0.00608 |
| Sonnet 5 | $0.00016 | $0.00243 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
content-engine 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Engine
Adapt one idea into content that reads as native to each platform, not a copy-paste of the same paragraph everywhere.
First Questions
Before drafting, clarify:
- Source asset — what are we adapting from (article, demo, memo, podcast, launch doc)?
- Audience — builders, investors, customers, operators, or general?
- Platform(s) — X, LinkedIn, TikTok, YouTube, newsletter, or multi-platform?
- Goal — awareness, conversion, recruiting, authority, launch support, or engagement?
If the user hasn't specified platform or audience and the ask is non-trivial, ask before drafting rather than guessing — a post written for the wrong audience has to be rewritten, not edited.
Core Rules
- Adapt for the platform. Never cross-post the same copy; a post's opening line, length, and structure should look different on each platform even when the underlying idea is identical.
- Hooks matter more than summaries. The first line has to earn the second line's attention — a factual summary opener ("Today we're excited to announce...") is a hook a reader has learned to skip.
- One clear idea per post. A post trying to carry three points lands none of them; split into a thread or a series instead.
- Specifics over slogans. A concrete number, name, or before/after beats an abstract claim ("cut p95 latency from 800ms to 120ms" beats "blazing fast").
- Keep the ask small and clear. One CTA, matched to platform norms and the stated goal — don't stack "follow, like, comment, and sign up" in one post.
Platform Guidance
| Platform | What to do differently |
|---|---|
| X | Open fast, one idea per post (or per tweet in a thread); keep links out of the main body when possible; no hashtag spam |
| Strong first line before the "see more" fold; short paragraphs; explicit framing around lessons, results, and takeaways | |
| TikTok / short video | First 3 seconds must interrupt attention; script around visuals, not narration; one demo, one claim, one CTA |
| YouTube | Show the result early, don't bury the payoff; structure by chapter; refresh the visual every 20-30 seconds |
| Newsletter | One clear lens per issue, not a bundle of unrelated items; skimmable section titles; the opening paragraph has to do real work, not just say "welcome back" |
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 · 79 lines · 78 tokens per session scan A 9b2f4900d070
content-engine is a skill published in the GitHub repository shennawardana23/skillme (2 stars, last pushed 11d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,216 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-31.
Other skills, from other repositories
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
skill-creator
Create, improve, evaluate, benchmark skills. Use when authoring a new skill, updating an existing one, running evals, or optimizing a skill's description for triggering. Don't use for invoking skills, writing prose, or scaffolding Python projects.
skill-index-updater
Add GitHub skill repos to the ASM index: clone, audit, eval, regenerate index, rebuild catalog, open PR. Use when given GitHub URLs to onboard. Don't use for authoring (skill-creator), improving (skill-auto-improver), or install (asm install).
hello-world
A minimal test skill that greets the user and demonstrates the ASM publish workflow.