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.
git clone --depth 1 https://github.com/kanaerulabs/growth-kitWrote 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/commands/kanaerulabs/growth-kit/devto)<a href="https://agentmods.dev/commands/kanaerulabs/growth-kit/devto"><img src="https://agentmods.dev/badge/commands/kanaerulabs/growth-kit/devto/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/commands/kanaerulabs/growth-kit/devto"><img src="https://agentmods.dev/badge/commands/kanaerulabs/growth-kit/devto.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.00011 | $0.01896 |
| Opus 5.5 | $0.00004 | $0.00758 |
| Sonnet 5.5 | $0.00002 | $0.00379 |
| Haiku 4.5 | $0.00001 | $0.00190 |
Grade A, and why
devto 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a Dev.to-optimized RSS feed that can be used to automatically import your blog posts to Dev.to.
What this does: Creates an RSS feed with HTML-encoded content that Dev.to can import and convert to their markdown format.
Process
1. Understand the Blog Structure
Scan the codebase to understand:
- Where are markdown blog posts stored?
- What frontmatter format is used?
- What's the blog base URL?
- Where are images/diagrams located?
Common blog structures:
src/content/blog/posts/{en,ja}/*.mdcontent/blog/*.mdposts/*.mdblog/*.md
2. Read All Blog Posts
Use Glob to find all markdown files:
- Search pattern:
**/*.mdin blog directories - Read each file with Read tool
- Extract frontmatter (title, description, date, author)
- Extract markdown content
For each post:
{
title: string,
description: string,
date: string,
author: string,
slug: string,
content: string (markdown),
url: string (full blog post URL)
}
3. Convert Markdown to HTML
Dev.to Requirements:
- Content must be HTML (in
<content:encoded>field) - All URLs must be absolute (not relative)
- Images must use absolute URLs
- Dev.to will convert the HTML back to markdown on their end
Conversion process:
- Convert markdown to HTML (use marked.js if available, or simple conversion)
- Make all image URLs absolute
- Make all links absolute
- Preserve code blocks and formatting
4. Generate RSS Feed
Create XML file with RSS 2.0 format:
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Blog Title</title>
<description>Blog Description</description>
<link>https://yourblog.com</link>
<atom:link href="https://yourblog.com/rss-devto.xml" rel="self" type="application/rss+xml"/>
<language>en</language>
<item>
<title>Post Title</title>
<link>https://yourblog.com/blog/post-slug</link>
<guid>https://yourblog.com/blog/post-slug</guid>
<pubDate>Mon, 01 Jan 2025 00:00:00 GMT</pubDate>
<description>Post description</description>
<content:encoded><![CDATA[
<!-- HTML content here with absolute URLs -->
]]></content:encoded>
<dc:creator>Author Name</dc:creator>
</item>
<!-- More items... -->
</channel>
</rss>
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 · 262 lines · 11 tokens per session scan A 51140d56e181
devto is a command published in the GitHub repository kanaerulabs/growth-kit (15 stars, last pushed 8mo ago), licensed MIT. It adds 11 tokens to every session and 1,896 once invoked, about $0.0000 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 commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
init
Install the formatters this repository needs, with every command visible before it runs.
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
brand-generate
Generate an on-brand document from a saved Brand Profile.