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 mgiovani/cc-arsenal --skill oss-launchgit clone --depth 1 https://github.com/mgiovani/cc-arsenalWrote 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/mgiovani/cc-arsenal/oss-launch)<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/oss-launch"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/oss-launch/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/mgiovani/cc-arsenal/oss-launch"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/oss-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 89 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 97 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00214 | $0.02507 |
| Opus 5.5 | $0.00086 | $0.01003 |
| Sonnet 5.5 | $0.00043 | $0.00501 |
| Haiku 4.5 | $0.00021 | $0.00251 |
Grade A, and why
oss-launch 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 22d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSS Launch
Take a private side project from "done" to a public GitHub launch in seven staged gates: pre-flight, review, brand, README, mention scrub, history rewrite (optional, hard-gated), public flip. Like ship, every stage reports the real command it ran and stops at the first gate that isn't met: never estimate a result, never skip a gate silently.
Track progress with TodoWrite (one line per stage) so the user sees where the launch train is if a gate stops it.
The stages
| # | Stage | Gate |
|---|---|---|
| 1 | Pre-flight | Repo is private; no leaked secrets; a license exists |
| 2 | Review | No unresolved Critical/High findings |
| 3 | Brand | (optional) logo/hero generated or reused |
| 4 | README + description | Value-prop-first README, topics set |
| 5 | Mention scrub | User confirms exactly what gets removed |
| 6 | History rewrite | Private only, ever-public check, explicit confirmation this turn |
| 7 | Public flip | Every earlier stage passed |
Stage 1: Pre-flight
gh repo view --json isPrivate,licenseInfo,forkCount,stargazerCount -q .: recordisPrivate; this is the launch's core assumption and Stage 6 rechecks it independently.- Secrets scan: run the same check
env-setup's Phase 6 does, grep tracked files and.env/git history for key/secret/password/token patterns (see that skill'sscan-patterns.mdreference if you need the full pattern set). Any hit stops the whole train: report the finding asfile:lineonly, never the matched value, and go no further. - License: check for
LICENSE/LICENSE.md/COPYINGat the repo root. Missing license is not an auto-fill, ask the user which license they want (MIT, Apache-2.0, etc.) before continuing; don't pick one for them.
Stage 2: Review
Invoke the review-code skill (via Skill, or a Task/Explore→sonnet subagent if that's unavailable) against the default branch. Any Critical/High finding stops the train: report it and let the user decide (fix and re-run, or explicitly accept the risk). Medium/Low findings are reported but don't block.
What ships with it
6 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.
- 22d ago Changed · -1 lines fd7394cfe2b0
- 1mo ago Changed 76d15cc8cf5c
- 1mo ago Changed · -4 tokens per session a23bbbc3e7fe
- 1mo ago Changed 86d2325ee2d5
- 1mo ago Changed · +1 lines 50d786259b4e
- 1mo ago First seen · 127 lines · 218 tokens per session scan A 53e16ddfddd0
oss-launch is a skill published in the GitHub repository mgiovani/cc-arsenal (8 stars, last pushed 2d ago), licensed MIT. It adds 214 tokens to every session and 2,507 once invoked, about $0.0009 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-08-31.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.