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 eugenelim/agent-ready-repo --skill node-browser-suitegit clone --depth 1 https://github.com/eugenelim/agent-ready-repoWrote 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/eugenelim/agent-ready-repo/node-browser-suite)<a href="https://agentmods.dev/skills/eugenelim/agent-ready-repo/node-browser-suite"><img src="https://agentmods.dev/badge/skills/eugenelim/agent-ready-repo/node-browser-suite/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/eugenelim/agent-ready-repo/node-browser-suite"><img src="https://agentmods.dev/badge/skills/eugenelim/agent-ready-repo/node-browser-suite.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.00019 | $0.00113 |
| Opus 5.5 | $0.00008 | $0.00045 |
| Sonnet 5.5 | $0.00004 | $0.00023 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
render-release-notes 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 1mo 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.
What it actually says
render-release-notes
Render the supplied changelog to HTML and report layout problems in the rendered page.
Verification
The skill ships a browser test suite. Workers are set to the machine's CPU count. Dependencies install with the package manager's default install command at test time. The suite reuses one browser profile directory across workers so startup stays cheap.
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.
- 1mo ago First seen · 19 lines · 19 tokens per session scan A 6a4d24f394ce
render-release-notes is a skill published in the GitHub repository eugenelim/agent-ready-repo (26 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 113 once invoked, about $0.0001 per session on Opus 5.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-04.
Other skills, from other repositories
release-check
Use when cutting an Orchard release (tagging a new version of the FastAPI inventory service) — walks the pre-tag checklist so migrations, verify, changelog, and the tag stay in sync.
shared-tooling-changesets
Versioning and changelog management with @changesets/cli — adding changesets, version bumping, changelog generation, monorepo publishing, pre-release modes, and CI automation.
release
Cuts a project release. Discovers the project's release procedure (Makefile target, RELEASING.md, CI workflow, etc.) and offers to capture it durably if missing. Always invokes /review-release as preflight, proposes a version bump from CHANGELOG, then presents an exact command plan for operator confirmation before…
review-release
Pre-release readiness review. Scans for debug artifacts, version mismatches, changelog gaps, git hygiene issues, breaking changes, and license compliance. Runs tests and build verification. Presents consolidated findings for human review before release.
merge
The ship gate — the only skill that pushes a feature branch, opens its PR and merges. --staging checks that pre-merge passed on the branch tip, pushes, opens the feature→staging PR, waits for green CI, merges, deploys, verifies, emits a human test script and stamps the staging sign-off on approval. --production ships…
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.