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 Varnan-Tech/opendirectory --skill tweet-thread-from-bloggit clone --depth 1 https://github.com/Varnan-Tech/opendirectoryWrote 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/varnan-tech/opendirectory/tweet-thread-from-blog)<a href="https://agentmods.dev/skills/varnan-tech/opendirectory/tweet-thread-from-blog"><img src="https://agentmods.dev/badge/skills/varnan-tech/opendirectory/tweet-thread-from-blog/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/varnan-tech/opendirectory/tweet-thread-from-blog"><img src="https://agentmods.dev/badge/skills/varnan-tech/opendirectory/tweet-thread-from-blog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 175 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00119 | $0.01620 |
| Opus 5 | $0.00060 | $0.00810 |
| Sonnet 5 | $0.00024 | $0.00324 |
| Haiku 4.5 | $0.00012 | $0.00162 |
Grade A, and why
tweet-thread-from-blog 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 10d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tweet Thread from Blog
Convert a blog post or article into a 7-10 tweet thread. One insight per tweet. Strong hook. CTA in the final tweet. Optionally post the thread directly to X via Composio.
Writing Style
Apply these rules to every tweet you write:
- Active voice only
- Conversational, like a person typed it on their phone
- Contractions required: don't, it's, won't, can't, I've
- Short sentences, one idea per tweet
- No em dashes — use a period or comma instead
- No semicolons
- No markdown or asterisks
- No hashtags anywhere in the thread
Banned words — do not use any of these: incredible, amazing, leveraging, synergize, game-changing, game changer, let's dive in, buckle up, it's worth noting, delve, harness, unlock, groundbreaking, cutting-edge, remarkable, paradigm, revolutionize, disruptive, transformative, thrilled, excited to share, powerful, innovative, comprehensive, actionable, crucial, vital, pivotal, elucidate, utilize, can, may, just, that, very, really, literally, actually, certainly, probably, basically, could, maybe
If a draft tweet contains any banned word, rewrite it before presenting.
CRITICAL RULE
Do not invent specifics. Every claim, stat, and example in the thread must come from the blog post. Never fabricate data, quotes, or outcomes.
Step 1: Check Setup
Confirm input is present. The user must provide one of:
- A blog post URL
- Pasted article text
If no input is present, ask: "What blog post or article should I turn into a thread? Share a URL or paste the content."
COMPOSIO_API_KEY is only needed for direct posting to X. Output-only mode works without it.
Step 2: Fetch and Extract Content
If input is a URL: Use WebFetch or Chrome DevTools MCP to fetch the page. Extract:
- Title
- Author name
- Publish date
- All body text
- Key statistics and data points
- Numbered lists or steps
- Subheadings
- Any quotes
If input is pasted text: Read it directly.
After fetching, identify:
- The single most surprising or counterintuitive insight
- 6-9 supporting insights, data points, or steps
- Any specific numbers, percentages, or concrete results
- The core argument or main takeaway
What ships with it
5 files 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.
- 10d ago First seen · 178 lines · 119 tokens per session scan A 6199ad1ff423
tweet-thread-from-blog is a skill published in the GitHub repository Varnan-Tech/opendirectory (637 stars, last pushed 24d ago), licensed MIT. It adds 119 tokens to every session and 1,620 once invoked, about $0.0006 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
content-style
Writing Reddit-native content that sounds human, avoids AI tells, and delivers value through structure and specificity. Applies to workshop posts, definitive model guides, research megathreads, and community FYI/update posts.
coding-worktree-recovery
Use this skill when coding-agent work is interrupted, an agent exits without a clean commit, multiple controllers target the same checkout, or the checkout produces inconsistent file/Git behavior.
macos-storage-management
Safely reclaim local Mac storage without mistaking cloud placeholders for resident data, losing File Provider content, or flattening metadata onto an incompatible external filesystem.
hermes-mnemosyne
Mnemosyne is Hermes' primary local-first memory engine — SQLite with vector + FTS5 hybrid search, 19+ tools, auto-consolidation, and a standalone CLI. It's a pip-installed plugin (not a built-in toolset) discovered via $HERMESHOME/plugins/mnemosyne/.
skill-auditor
Audit any Hermes skill file and assign a quality grade based on clarity, completeness, tool guidance, and shareability. Returns specific fix suggestions ranked by impact.
marketplace-purchase-vetting
Use this when the user asks whether a local listing is a scam, "too good to be true," worth looking at, or a good deal. Also use this when he asks you to find options — search/discover candidates, then vet the best ones. The goal is not a generic buying guide; it is a practical risk read with clear next steps.