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 skills add jonathimer/devmarketing-skills --skill dev-tool-directory-listingsgit 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/dev-tool-directory-listings)<a href="https://agentmods.dev/skills/jonathimer/devmarketing-skills/dev-tool-directory-listings"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/dev-tool-directory-listings.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.1 | $0.00091 | $0.01930 |
| Opus 5 | $0.00046 | $0.00965 |
| Sonnet 5 | $0.00018 | $0.00386 |
| Haiku 4.5 | $0.00009 | $0.00193 |
Grade A, and why
dev-tool-directory-listings 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 8d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Tool Directory Listings
Overview
Developers discover tools through curated directories, GitHub awesome-lists, and recommendation threads. Unlike general business directories, developer directories are often community-maintained, have genuine editorial standards, and drive qualified traffic. Getting listed requires meeting quality bars and contributing authentically to these communities.
This skill covers identifying valuable directories, submitting effectively, and maintaining your presence over time.
Understanding the Directory Landscape
Types of Developer Directories
GitHub Awesome Lists Community-curated lists organized by technology or category. Examples:
- awesome-python
- awesome-react
- awesome-selfhosted
- awesome-developer-tools
These have high credibility because they're community-vetted and contributions are public.
Curated Directories Editorially maintained directories with submission processes:
- AlternativeTo
- Product Hunt (for launches)
- StackShare
- LibHunt
- ToolsForCreators
Category-Specific Directories Niche directories for specific developer needs:
- NoCodeDevs (no-code tools)
- RemoteTools (remote work tools)
- DevHunt (dev tool launches)
- APIList (API directories)
Package Registries If you have libraries, these are essential:
- npm (JavaScript)
- PyPI (Python)
- crates.io (Rust)
- Go packages
- Maven Central (Java)
Which Directories Actually Matter
Not all directories drive value. Prioritize based on:
- Traffic quality: Do developers you want actually use this?
- Domain authority: Does a backlink help SEO?
- Maintenance: Is the directory actively maintained?
- Competition: Are similar tools listed?
- Referral tracking: Can you measure actual visits?
High-value directories to prioritize:
- GitHub awesome-lists in your category
- StackShare
- AlternativeTo
- Product Hunt (for major launches)
- Category-specific directories with engaged communities
Often low-value:
- Generic "software directories"
- Abandoned lists with no recent updates
- Directories that accept anything
- Link farms disguised as directories
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.
- 8d ago First seen · 312 lines · 91 tokens per session scan A a63871578240
dev-tool-directory-listings is a skill published in the GitHub repository jonathimer/devmarketing-skills (86 stars, last pushed 6mo ago), licensed MIT. It adds 91 tokens to every session and 1,930 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…