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 BjornMelin/dev-skills --skill repo-modernizergit clone --depth 1 https://github.com/BjornMelin/dev-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/bjornmelin/dev-skills/repo-modernizer)<a href="https://agentmods.dev/skills/bjornmelin/dev-skills/repo-modernizer"><img src="https://agentmods.dev/badge/skills/bjornmelin/dev-skills/repo-modernizer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bjornmelin/dev-skills/repo-modernizer"><img src="https://agentmods.dev/badge/skills/bjornmelin/dev-skills/repo-modernizer.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.01026 |
| Opus 5 | $0.00018 | $0.00513 |
| Sonnet 5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
repo-modernizer 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
31 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.
- agents/openai.yaml 521 B
- references/00-variant-index.md 1.5 KB
- references/bun-first.md 1.9 KB
- references/dependency-decision-matrix.md 5.2 KB
- references/execution-prompt.md 12 KB
- references/framework-lane-selection.md 5.8 KB
- references/gh-deps-command-mapping.md 486 B
- references/gh-deps-compatibility-policy.md 734 B
- references/gh-deps-github-api-endpoints.md 926 B
- references/gh-deps-report-spec.md 994 B
- references/gh-deps-troubleshooting.md 863 B
- references/gh-deps-workflow.md 1.3 KB
- references/plan-first.md 1.7 KB
- references/pnpm-turbo-monorepo.md 2.0 KB
- references/report-template.md 3.7 KB
- references/verification-matrix.md 5.1 KB
- scripts/collect_deps.py 7.9 KB runs code
- scripts/detect_repo.py 11 KB runs code
- scripts/fallback_registry_fetch.py 1.8 KB runs code
- scripts/gh_compare_notes.py 2.0 KB runs code
- scripts/gh_deps_intel.py 24 KB runs code
- scripts/gh_rate_limit_diag.py 424 B runs code
- scripts/gh_release_diff.py 1.1 KB runs code
- scripts/gh_release_fetch.py 12 KB runs code
- scripts/impact_analyzer.py 3.6 KB runs code
- scripts/outdated_probe.py 9.8 KB runs code
- scripts/render_report.py 9.2 KB runs code
- scripts/repo_resolver.py 9.8 KB runs code
- scripts/runtime_policy.py 5.3 KB runs code
- scripts/upgrade_one_dep.py 1.6 KB runs code
- scripts/utils.py 4.2 KB runs code
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.
- 9d ago First seen · 103 lines · 36 tokens per session scan A 11dfe0a04b5b
repo-modernizer is a skill published in the GitHub repository BjornMelin/dev-skills (7 stars, last pushed 4d ago), with no licence file. It adds 36 tokens to every session and 1,026 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
contribute-to-eliza
Finish and prove a scoped elizaOS GitHub issue, or independently review and repair an open elizaOS pull request. Use when contributing compute to elizaOS by selecting unclaimed work, implementing or reviewing changes, adding real tests and evidence, validating artifacts, or preparing a contribution for maintainer…
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
competitor-product-monitor
Monitor competitor product releases and new feature announcements. Use this skill when the user wants to track what competitors are shipping, find the latest product launches in their industry, or generate a competitor release report. Triggers include phrases like "track competitor releases", "what are my competitors…
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
lean-review
CocoLean diff-scoped over-engineering audit — scans uncommitted git diff and applies five classification tags (delete/stdlib/native/yagni/shrink) to identify unnecessary surface area before commit.