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 Varnan-Tech/opendirectory --skill dx-roastergit clone --depth 1 https://github.com/Varnan-Tech/opendirectoryWrote 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/varnan-tech/opendirectory/dx-roaster)<a href="https://agentmods.dev/skills/varnan-tech/opendirectory/dx-roaster"><img src="https://agentmods.dev/badge/skills/varnan-tech/opendirectory/dx-roaster.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.00130 | $0.02730 |
| Opus 5 | $0.00065 | $0.01365 |
| Sonnet 5 | $0.00026 | $0.00546 |
| Haiku 4.5 | $0.00013 | $0.00273 |
Grade A, and why
dx-roaster 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 7d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dx-roaster
Roasts a GitHub repo's developer experience. Produces four files: roast.md, action-plan.md, ideal-readme.md, score.json. Built for OSS maintainers and dev-tool founders preparing for Show HN, Product Hunt, or any launch where the first five minutes matter.
Critical rules (read before every run)
-
Read all three reference files BEFORE scoring.
references/scoring-rubric.md,references/roast-voice-guide.md,references/readme-template.md. The rubric is non-negotiable — use the exact 10 dimensions. -
Score every dimension on the 0–10 scale. Never skip. Missing data = score 0, not "N/A".
-
Roast must cite specific findings. Quote bad lines verbatim. Reference file paths. Cite line numbers when possible. Never write generic platitudes like "documentation could be better".
-
Tone matters. Default
honest. Switch voice perreferences/roast-voice-guide.md. Brutal is funny but never personal. Kind is encouraging but still specific. -
Action plan is impact-ranked, not severity-ranked. Use
impact × (1 / effort). A 5-minute fix that adds 10 points ranks above a 2-hour fix that adds 12 points. -
Never invent URLs. When writing
ideal-readme.md, use<placeholder>syntax for missing links. Roast will tell maintainer to fill in. -
Never name maintainers or contributors. Roast the work, not the people.
-
Output exactly four files in
dx-roast/. Do not write to other locations. Do not skip files.
Step 1: Intake
Required:
repo— local path (default.) ORhttps://github.com/owner/repoURL
Optional:
| Parameter | Default | Description |
|---|---|---|
tone |
honest |
brutal / honest / kind |
output_dir |
dx-roast/ |
Where to write the 4 output files |
compare_to |
none | Optional second repo URL for benchmark comparison |
If repo is a URL: clone to a temp dir using git clone <url> /tmp/dx-roast-<short-hash>. Scan from there. Delete temp dir after run.
What ships with it
4 files 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.
- 7d ago First seen · 272 lines · 130 tokens per session scan A 618f0080017e
dx-roaster is a skill published in the GitHub repository Varnan-Tech/opendirectory (635 stars, last pushed 21d ago), licensed MIT. It adds 130 tokens to every session and 2,730 once invoked, about $0.0006 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
specification-compliance-review
Use this skill when an implementation is described as partial, passing, or complete and the task is to determine whether it actually satisfies an explicit specification. This is not a generic code review and not a re-run of the test suite. The central question is: does every normative requirement have both a correct…
github-code-review
Perform code reviews on local changes before pushing, or review open PRs on GitHub. Most of this skill uses plain git — the gh/curl split only matters for PR-level interactions.
github-pr-workflow
Complete guide for managing the PR lifecycle. Each section shows the gh way first, then the git + curl fallback for machines without gh.
github-repo-audit
A review process for checking whether a GitHub repository and its release materials are complete and consistent.
subagent-driven-development
Execute implementation plans by dispatching fresh subagents per task with systematic two-stage review.
dustbringer
Delete what is dead, split what is overgrown, and pay down structural debt.