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 bntvllnt/agent-skills --skill oss-readinessgit clone --depth 1 https://github.com/bntvllnt/agent-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/bntvllnt/agent-skills/oss-readiness)<a href="https://agentmods.dev/skills/bntvllnt/agent-skills/oss-readiness"><img src="https://agentmods.dev/badge/skills/bntvllnt/agent-skills/oss-readiness/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/bntvllnt/agent-skills/oss-readiness"><img src="https://agentmods.dev/badge/skills/bntvllnt/agent-skills/oss-readiness.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.00106 | $0.02385 |
| Opus 5 | $0.00053 | $0.01192 |
| Sonnet 5 | $0.00021 | $0.00477 |
| Haiku 4.5 | $0.00011 | $0.00238 |
Grade A, and why
oss-readiness 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 10d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSS Readiness — Public Release Gate
Audit a repository for open-source release basics. Scaffold missing public docs/templates.
Generate AI-friendly docs (llms.txt, llms-full.txt). Validate CI. Sync version references.
Portability Rules
This skill must stay harness-agnostic and maintainer-agnostic:
- Accept natural-language prompts and slash-command shorthand as equivalent entry points.
- Keep
AGENTS.mdas the canonical agent-instructions file when one is scaffolded. - Treat harness-specific files such as
CLAUDE.md,.cursorrules,.windsurfrules,codex.md, or.opencode/configas optional aliases/mirrors — never the only supported path. - Use placeholders in generated files. Never hardcode links, social handles, org names, or contact methods from this repository.
- Never invent maintainer contact channels. If the project does not provide one, leave a clear placeholder or omit the optional section.
Required Capabilities
| Capability | Used For | Required | Fallback |
|---|---|---|---|
| File read/write/edit | Audit and scaffold docs/templates | Yes | — |
| Shell access | git/gh/grep/find-based checks | Recommended | Manual file inspection |
git |
Repo metadata, tags, tracked-file checks | Recommended | Filesystem-only audit |
gh |
GitHub metadata, PR/issue/security settings | Optional | Report as unchecked/manual |
node or python |
Manifest/version extraction helpers | Optional | Grep/parse text manually |
The skill still works without shell tooling. Shell commands are accelerators, not requirements.
Entry Points
Use either natural language or shorthand. Route both to the same workflow.
| Intent | Example prompts | Route |
|---|---|---|
| Full audit | audit OSS readiness, /oss |
references/checklist.md |
| Scaffold missing files | scaffold missing OSS files, /oss fix |
references/checklist.md |
| Generate LLM docs | generate llms.txt, /oss llms |
references/llms-generation.md |
| Sync version refs | bump stale version refs in docs, /oss bump |
references/version-sync.md |
| Validate CI | check OSS CI readiness, /oss ci |
references/ci-validation.md |
| Review release title / notes / announcement framing | audit release messaging, is this a good OSS release title? |
references/release-messaging.md |
What ships with it
16 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.
- README.md 2.2 KB
- references/checklist.md 9.3 KB
- references/ci-validation.md 11 KB
- references/llms-generation.md 6.8 KB
- references/release-messaging.md 2.7 KB
- references/version-sync.md 3.7 KB
- templates/AGENTS.md 2.5 KB
- templates/CODE_OF_CONDUCT.md 2.8 KB
- templates/CONTRIBUTING.md 2.4 KB
- templates/issue-template-bug.md 2.2 KB
- templates/issue-template-feature.md 1.0 KB
- templates/llms-full.txt.md 769 B
- templates/llms.txt.md 722 B
- templates/pr-template.md 739 B
- templates/README.md 545 B
- templates/SECURITY.md 1.4 KB
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.
- 10d ago First seen · 222 lines · 106 tokens per session scan A d71d87612a4f
oss-readiness is a skill published in the GitHub repository bntvllnt/agent-skills (16 stars, last pushed 3mo ago), licensed MIT. It adds 106 tokens to every session and 2,385 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
release
Verify, sweep docs, cut a version — then hand the release sequence back.
deploy-automation
Workflows and best practices for CI/CD automation, deployment strategies, and production releases. Use when implementing or improving deployment pipelines, managing environments, or planning production releases.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASERULE.md, then guides the release.
comet-archive
A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.