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 commands/amirtaherkhani/dev-io-mcp/dev.iogit clone --depth 1 https://github.com/amirtaherkhani/dev-io-mcpWrote 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/amirtaherkhani/dev-io-mcp/dev.io)<a href="https://agentmods.dev/commands/amirtaherkhani/dev-io-mcp/dev.io"><img src="https://agentmods.dev/badge/commands/amirtaherkhani/dev-io-mcp/dev.io.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.00016 | $0.00230 |
| Opus 5 | $0.00008 | $0.00115 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
dev.io 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 3d 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
Use the dev-io MCP server and the dev-io skill for this request.
Route the command from $ARGUMENTS:
publishorpost: summarize the current conversation or supplied document, redact secrets, and callpublish_post.list: calllist_postsand present the file names.readorshow: callread_postfor the requested file.infoorstats: callget_post_infofor the requested file.view,like, orcomment: callrecord_post_eventwith the matching event.
For publishing, return the local file path and clearly separate local creation from a DEV.to result. Never claim remote publication unless the MCP response contains remote.published: true and an article ID or URL. Never expose API keys or private conversation data.
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.
- 3d ago First seen · 17 lines · 16 tokens per session scan A 292c1a3baf2a
dev.io is a command published in the GitHub repository amirtaherkhani/dev-io-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 230 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-31.
Other commands, from other repositories
devto
Generate Dev.to-optimized RSS feed for automatic article import.
all
Generate content for all platforms (X, LinkedIn, Medium, Dev.to) from a single input.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.