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 agentmods add skills/fiveonecode/agent-skills/public-source-release-auditnpx skills add fiveonecode/agent-skills --skill public-source-release-auditgit clone --depth 1 https://github.com/fiveonecode/agent-skillsWhat 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 | $0.00058 | $0.01116 |
| Opus 5 | $0.00029 | $0.00558 |
| Sonnet 5 | $0.00012 | $0.00223 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
public-source-release-audit scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
'print ERB::Util.url_encode(ARGV.fetch(0))' "$default_branch")" How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public-Source Release Audit
Use this skill to answer a narrow question honestly: does the current source candidate contain a supported high-confidence leak, and have the separate human and GitHub-native release checks been confirmed?
Automated Current-Source Check
Run the repository's own verifier when it exists. Then run:
ruby <skill-directory>/scripts/check_current_source.rb <repository>
The checker reads exact Git-index blobs so an unstaged replacement cannot hide the candidate. It also scans tracked and non-ignored untracked worktree files for early feedback. It reports only paths and finding categories, never the matched content.
The supported lexical forms are deliberately small:
- PEM, OpenSSH, PGP, and PuTTY private-key headers;
- GitHub
ghp_,gho_,ghu_,ghs_,ghr_, andgithub_pat_token prefixes; - AWS
AKIA/ASIAaccess-key IDs and canonical named 40-character secret access-key values; - OpenAI
sk-andsk-proj-key prefixes; - explicit
Authorization: Bearerheader or map values; and - literal, commonly source-escaped, or
file://-wrapped rooted POSIX familiesUsers/<name>,var/root,private/var/root,home/<name>, androot, plus drive-letterUsers\\<name>paths, including UTF-8 profile names and bounded environment and command-option values.
The home-path rule covers literal paths and common source escaping for POSIX slashes and Windows backslashes. It does not decode URL-encoded content. The credential map rules inspect direct source text; they do not decode nested escaped documents.
Stage all intended release changes before relying on the candidate result. Ignored files and submodule contents are outside this check. The checker does not inspect Git history. Git LFS pointers fail the check because their external objects require separate review. Missing index blobs, including unavailable partial-clone objects, fail without network fetching. A symlink's own target text is scanned, while a symlinked parent component fails without reading outside the repository. Git's optional locks are disabled so read-only index operations do not freshen split-index metadata, and inherited Git trace-file destinations are cleared. BOM-marked UTF-16 source also requires separate review; the checker does not transcode or unpack content.
What ships with it
2 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.
- 2d ago First seen · 106 lines · 58 tokens per session scan A a166c8587e64
public-source-release-audit is a skill published in the GitHub repository fiveonecode/agent-skills (19 stars, last pushed 10d ago), licensed MIT. It adds 58 tokens to every session and 1,116 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.