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 jonathimer/devmarketing-skills --skill dev-to-hashnodegit clone --depth 1 https://github.com/jonathimer/devmarketing-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/jonathimer/devmarketing-skills/dev-to-hashnode)<a href="https://agentmods.dev/skills/jonathimer/devmarketing-skills/dev-to-hashnode"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/dev-to-hashnode/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/jonathimer/devmarketing-skills/dev-to-hashnode"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/dev-to-hashnode.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.00059 | $0.02608 |
| Opus 5.5 | $0.00024 | $0.01043 |
| Sonnet 5.5 | $0.00012 | $0.00522 |
| Haiku 4.5 | $0.00006 | $0.00261 |
Grade A, and why
dev-to-hashnode 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 1mo 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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev.to & Hashnode Publishing
Developer blogging platforms offer built-in audiences of hundreds of thousands of developers. This skill covers cross-posting strategy, platform-specific optimization, and building followers on Dev.to and Hashnode.
Before You Start
- Read
.agents/developer-audience-context.mdif it exists - Decide your canonical URL strategy (important for SEO)
- Create accounts on both platforms to reserve your username
- Understand: These platforms reward consistency and engagement
Platform Comparison
Dev.to vs Hashnode
| Feature | Dev.to | Hashnode |
|---|---|---|
| Monthly visitors | ~10M+ | ~3M+ |
| Custom domain | No (subdomain only) | Yes (free) |
| Canonical URL support | Yes | Yes |
| SEO benefits | High domain authority | Your domain gets SEO |
| Monetization | No native | Sponsors, newsletter |
| Newsletter | No | Built-in |
| Series support | Yes | Yes |
| Code highlighting | Excellent | Excellent |
| Community features | Strong (reactions, comments) | Growing |
| Audience | Broader, more beginners | More senior, focused |
When to Use Each
| Use Dev.to when | Use Hashnode when |
|---|---|
| Maximum reach is priority | Building your own brand |
| Targeting beginners/mid-level | Want custom domain SEO |
| Community engagement matters | Building email list |
| Quick validation of content | Long-term content strategy |
| Don't have your own blog | Supplementing your main blog |
Cross-Posting Strategy
The Canonical URL Decision
| Strategy | Pros | Cons |
|---|---|---|
| Original on your blog | SEO to your domain, full control | Platforms may rank lower |
| Original on Dev.to | Maximum initial reach | No SEO to your domain |
| Original on Hashnode (custom domain) | SEO + platform reach | Smaller initial audience |
Best Practice: Your Blog + Cross-Post
- Publish on your blog first — This is canonical
- Wait 1-2 days — Let Google index your original
- Cross-post to Dev.to — Set canonical URL to your blog
- Cross-post to Hashnode — Set canonical URL to your blog
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.
- 1mo ago First seen · 385 lines · 59 tokens per session scan A 6944ae82bad7
dev-to-hashnode is a skill published in the GitHub repository jonathimer/devmarketing-skills (87 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 2,608 once invoked, about $0.0002 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.