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 alivirgo/Major-AI-Skills --skill github-packages-npmgit clone --depth 1 https://github.com/alivirgo/Major-AI-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/alivirgo/major-ai-skills/github-packages-npm)<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/github-packages-npm"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/github-packages-npm/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/alivirgo/major-ai-skills/github-packages-npm"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/github-packages-npm.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.00026 | $0.00847 |
| Opus 5 | $0.00013 | $0.00424 |
| Sonnet 5 | $0.00005 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
github-packages-npm 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 yesterday.
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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Packages (npm) AI Skill Guide
Overview & Engine Architecture
GitHub Packages hosts npm packages under https://npm.pkg.github.com tied to a GitHub user or organization. Publish with publishConfig and a scoped name (@org/pkg); authenticate with GITHUB_TOKEN in Actions or a PAT with read:packages/write:packages locally. Agents configure .npmrc correctly, avoid leaking tokens, and align package permissions with repo visibility.
package.json (name @org/pkg)
-> npm publish
-> npm.pkg.github.com
Consumers -> .npmrc (@org:registry=...) + token
When to use this skill
- Publishing private or internal npm libraries to GitHub Packages
- Consuming
@org/*packages in apps and Actions - Migrating from npmjs private registries
- Debugging 401/403 publish or install failures
Operational directives
- Scope packages to the org (
@myorg/utils); set"registry": "https://npm.pkg.github.com"inpublishConfig. - Never commit tokens; use
NODE_AUTH_TOKEN/GITHUB_TOKENenv substitution in.npmrc. - Grant least package permissions;
GITHUB_TOKENwrite is limited to the current repo unless workflows are configured otherwise. - Version with semver; prefer CI publish on tagged releases.
- Document install steps for external contributors who need PATs.
publishConfig sketch
{
"name": "@acme/sdk",
"version": "1.4.0",
"publishConfig": {
"registry": "https://npm.pkg.github.com"
}
}
.npmrc sketches
# project or user level - token via env
@acme:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
# GitHub Actions
- uses: actions/setup-node@v4
with:
registry-url: https://npm.pkg.github.com
scope: "@acme"
- run: npm publish
env:
NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Common failures
| Symptom | Likely cause | Fix |
|---|---|---|
| 401 on install | Missing/invalid token | PAT with read:packages or SSO authorize |
| 403 on publish | Token lacks write / wrong repo | write:packages + package repo permissions |
| Package not found | Wrong scope registry mapping | @org:registry=https://npm.pkg.github.com |
| Duplicate version | Republish same semver | Bump version; do not force overwrite |
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.
- yesterday Changed · -10 tokens per session 6a19168e982f
- 7d ago First seen · 99 lines · 36 tokens per session scan A 54712fc46f6e
github-packages-npm is a skill published in the GitHub repository alivirgo/Major-AI-Skills (1 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 847 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
antigravity-workflows-v2
Antigravity Workflows workflow skill. Use this skill when the user needs Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA and the operator should preserve the upstream workflow, copied support files, and provenance before merging…
npm-docs
Use this skill whenever the user asks about npm, package management, publishing packages, semantic versioning, npm CLI commands, or Node.js dependencies. Covers npm 12.x including the registry, scopes, organizations, security (audit, provenance, 2FA), CI/CD integration, workspaces, scripts, .npmrc configuration, and…
antigravity-workflows
Antigravity Workflows workflow skill. Use this skill when the user needs Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA and the operator should preserve the upstream workflow, copied support files, and provenance before merging…
mysql-expert
Design, optimize, and maintain MySQL databases. Covers schema design, indexing strategies, query optimization, replication, and performance tuning.