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/developer-adsnpx skills add jonathimer/devmarketing-skills --skill developer-adsgit clone --depth 1 https://github.com/jonathimer/devmarketing-skillsWhat 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.00097 | $0.02570 |
| Opus 5 | $0.00048 | $0.01285 |
| Sonnet 5 | $0.00019 | $0.00514 |
| Haiku 4.5 | $0.00010 | $0.00257 |
Grade A, and why
developer-ads 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.
How it starts
The opening of the file, as written. The whole thing — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Ads
Overview
Most advertising doesn't work for developers. They use ad blockers, distrust marketing, and share bad experiences widely. But targeted advertising on developer-specific platforms—done thoughtfully—can drive qualified awareness and traffic.
This skill covers the platforms that actually reach developers, how to create ads that don't trigger immediate dismissal, and how to measure whether your spend is working.
Why Most Ads Don't Reach Developers
The Ad Blocker Problem
Estimates suggest 50-70% of developers use ad blockers. This makes most display advertising ineffective:
- Google Display Network: Heavily blocked
- Facebook/Instagram: Limited developer targeting
- General programmatic: Low reach, wrong audience
Developer Ad Resistance
Even when ads reach developers, they face skepticism:
- Banner blindness is extreme
- Marketing language triggers instant dismissal
- Developers share bad ads as cautionary tales
- Trust is hard to build, easy to lose
What Does Work
Advertising that reaches developers successfully:
- Contextual placement: Ads on sites developers already trust
- Value-first messaging: Leading with what you do, not superlatives
- Technical credibility: Ads that show you understand the audience
- Native formats: Newsletter mentions, sponsored content
Platform-by-Platform Guide
Carbon Ads
What it is: Native advertising network for developer and design websites
Where ads appear:
- Developer documentation sites
- Tech blogs
- Developer tools
- Open source project sites
Why it works:
- Non-intrusive design
- Respected by developers
- Often not blocked
- Highly contextual placement
Costs:
- CPM-based pricing
- Typically $2-5 CPM
- Minimum budgets vary
- Direct buys for premium sites
Best practices:
- Simple, text-focused creative
- Clear value proposition
- Relevant to site context
- No hype language
Limitations:
- Limited targeting options
- Cannot always choose specific sites
- Creative restrictions
- Availability varies
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.
- 3d ago First seen · 439 lines · 97 tokens per session scan A b6fd501cf171
developer-ads is a skill published in the GitHub repository jonathimer/devmarketing-skills (85 stars, last pushed 6mo ago), licensed MIT. It adds 97 tokens to every session and 2,570 once invoked, about $0.0005 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…