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/jonathimer/devmarketing-skills/x-devsnpx skills add jonathimer/devmarketing-skills --skill x-devsgit 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/x-devs)<a href="https://agentmods.dev/skills/jonathimer/devmarketing-skills/x-devs"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/x-devs.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.00063 | $0.02723 |
| Opus 5 | $0.00032 | $0.01362 |
| Sonnet 5 | $0.00013 | $0.00545 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
x-devs 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.
How it starts
The opening of the file, as written. The whole thing — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X/Twitter for Developers
Twitter/X remains the real-time pulse of the developer community. This skill covers thread structure, code screenshots, engagement tactics, and building an authentic developer following without being cringe.
Before You Start
- Read
.agents/developer-audience-context.mdif it exists - Audit your current X presence (bio, pinned, recent posts)
- Understand: Developer Twitter rewards authenticity and technical depth
Understanding Dev Twitter
Who's on Dev Twitter
| Segment | What they share | What they consume |
|---|---|---|
| Open source maintainers | Project updates, war stories | Industry news, peer projects |
| Tech leads | Team learnings, hiring | Architecture, management |
| Indie hackers | Building in public, MRR | Growth tactics, tools |
| DevRel | Content, events, community | Trends, developer sentiment |
| Framework authors | Updates, opinions | Feedback, community vibes |
| Learning devs | Questions, progress | Tutorials, inspiration |
What Works on Dev Twitter
| Content type | Engagement level | Notes |
|---|---|---|
| Technical threads | High | Deep dives get saved/shared |
| Code screenshots | High | Visual, scannable |
| Hot takes | High (risky) | Can backfire spectacularly |
| Building in public | High | Journey > destination |
| Memes | Medium-high | Know your audience |
| Announcements | Medium | Better with context |
| Tutorial links | Medium | Need compelling hook |
| Retweets with comment | Low-medium | Add real value |
| Plain links | Low | Algorithm deprioritizes |
The Algorithm (As We Understand It)
| Factor | Impact |
|---|---|
| Replies in first hour | High — signals engagement |
| Time spent on post | High — threads > tweets |
| Profile visits from post | High — interesting content |
| Bookmarks | High — "save for later" |
| Retweets | Medium — distribution |
| Likes | Medium — engagement signal |
| Link clicks | Low — X wants you on platform |
| External links | Negative — deprioritized |
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.
- 4d ago First seen · 407 lines · 63 tokens per session scan A 27233547b5a9
x-devs is a skill published in the GitHub repository jonathimer/devmarketing-skills (86 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 2,723 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…