Borrowing it
Nothing to install: this file belongs to IntelligentElectron/universal-netlist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/IntelligentElectron/universal-netlist/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/IntelligentElectron/universal-netlistWrote 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/intelligentelectron/universal-netlist/release)<a href="https://agentmods.dev/skills/intelligentelectron/universal-netlist/release"><img src="https://agentmods.dev/badge/skills/intelligentelectron/universal-netlist/release/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/intelligentelectron/universal-netlist/release"><img src="https://agentmods.dev/badge/skills/intelligentelectron/universal-netlist/release.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 69 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.
- medium Excessive Agency · line 41 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00064 | $0.02770 |
| Opus 5.5 | $0.00026 | $0.01108 |
| Sonnet 5.5 | $0.00013 | $0.00554 |
| Haiku 4.5 | $0.00006 | $0.00277 |
Grade A, and why
release 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 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.
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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Committing
Include ALL changes
The user works in parallel with you. When asked to commit, include ALL changes in the working tree, not just the ones you made. The user's manual edits are equally important. Always run git status first and review everything.
Workflow
- Run
git status(never use-uall) andgit diff --statto see the full picture - Run
git log --oneline -5to match the repository's commit message style - Review ALL changes, both yours and the user's, to understand the full scope
- Stage ALL relevant files. Do not cherry-pick only your changes
- Do NOT stage files that contain secrets (
.env, credentials, keys) - Warn the user if they ask to commit such files
- Do NOT stage files that contain secrets (
- Draft a commit message:
- Format:
type: description(e.g.,feat:,fix:,chore:,refactor:,docs:,test:) - Focus on the "why", not the "what"
- Keep it concise (1-2 sentences)
- Format:
- Commit using a HEREDOC for clean formatting:
git commit -m "$(cat <<'EOF' type: description EOF )" - NEVER add Claude Code or any other AI assistant as co-author or author
- NEVER use
--no-verifyto skip hooks unless the user explicitly asks - If pre-commit hooks fail, fix the issue and create a NEW commit (do not amend)
Grouping commits
For large changesets, plan multiple logical commits. After the first commit passes hooks cleanly, subsequent commits can use --no-verify to speed things up.
Pushing
- Push without asking. The PR and its checks are the review gate, not a confirmation prompt
- Use
git pushfor tracked branches - Use
git push -u origin <branch>for new branches - NEVER force push to
main/master
Merging
If a PR's work is fully done and verified, merge it. Do not leave finished work sitting open waiting for permission, and do not ask whether to merge something that is complete and green.
Done and verified means: the change does what the PR says, build is green, and any
claim the PR makes about behavior has been checked against real data rather than asserted.
The PR description carries the ## Decision tables and ## Verification sections that
Pull Requests requires. A PR that is still exploratory, or whose effect has not been measured, is not done — say
what is missing instead of merging it.
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 Changed · +1 lines 4364a72988cd
- 20d ago Changed · +40 lines 9ba68909c3df
- 1mo ago Changed · +38 lines 324f9e4d3724
- 1mo ago Changed · +38 lines 77923db7cad2
- 2mo ago First seen · 123 lines · 64 tokens per session scan A 1f80caef2084
release is a skill published in the GitHub repository IntelligentElectron/universal-netlist (56 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 2,770 once invoked, about $0.0003 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-30.
Other skills, from other repositories
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.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.