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 agentmods add skills/turmyshevd/openclawgotchi/devtonpx skills add turmyshevd/openclawgotchi --skill devtogit clone --depth 1 https://github.com/turmyshevd/openclawgotchiWrote 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/turmyshevd/openclawgotchi/devto)<a href="https://agentmods.dev/skills/turmyshevd/openclawgotchi/devto"><img src="https://agentmods.dev/badge/skills/turmyshevd/openclawgotchi/devto.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00341 |
| Opus 5 | $0.00006 | $0.00170 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
Dev.to Publishing 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 4d 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.
What it actually says
Dev.to Publishing Skill
Allows the bot to write, edit, and publish articles to Dev.to.
Capabilities
- Post Article: Create new drafts or published articles
- Update Article: Edit existing articles
- List Articles: See what you've published
Configuration
Requires DEVTO_API_KEY in .env.
Key can be generated at https://dev.to/settings/extensions.
Tools
post_devto_article(title, content, tags, published)
Creates a new article.
title: Title of the articlecontent: Markdown bodytags: List of tags (e.g.["python", "bot"])published:Trueto publish,Falsefor draft (default)
list_devto_articles()
Lists your recent published articles.
update_devto_article(id, ...)
Update an article by ID.
🛡️ Safety Protocol
- Draft First: Always create articles with
published=False(draft) unless the user explicitly orders you to "publish immediately". - Review: Ask the user to review the draft URL before flipping the switch to
published=True. - No Secrets: Never put
.envvalues or private IPs in articles.
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.
- 4d ago First seen · 50 lines · 13 tokens per session scan A a1096c1ab375
Dev.to Publishing is a skill published in the GitHub repository turmyshevd/openclawgotchi (48 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 341 once invoked, about $0.0001 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
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.
dev-workflow
The complete development workflow for SkillHub contributors including local dev, staging validation, testing, and PR creation. Ensures agents follow the correct sequence of steps.
daily-standup-journal
Generate concise daily standups, reflection prompts, and weekly retrospectives for individuals or teams. Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in without assuming prior history.
study-strategy-selector
Recommend practical study strategies matched to the material, learning goal, assessment, time, and learner constraints. Use for revision planning, homework routines, independent study, replacing ineffective habits, or adapting recall, spacing, explanation, and practice activities.
api-and-namespace-design
API design conventions, namespace coordinate system, RBAC roles, ClawHub compatibility layer, OpenAPI contract sync rules, and CSRF/session handling.
backend-module-structure
Rules for the SkillHub backend Maven multi-module clean architecture. Ensures agents place new code in the correct module and respect dependency direction.