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 X-School-Academy/skill-pilot --skill dev-swarm-npm-publishgit clone --depth 1 https://github.com/X-School-Academy/skill-pilotWrote 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/x-school-academy/skill-pilot/dev-swarm-npm-publish)<a href="https://agentmods.dev/skills/x-school-academy/skill-pilot/dev-swarm-npm-publish"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-npm-publish/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/x-school-academy/skill-pilot/dev-swarm-npm-publish"><img src="https://agentmods.dev/badge/skills/x-school-academy/skill-pilot/dev-swarm-npm-publish.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.00039 | $0.00624 |
| Opus 5.5 | $0.00016 | $0.00250 |
| Sonnet 5.5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
dev-swarm-npm-publish 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 16d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Builder - NPM Publish
This skill provides a repeatable process for publishing packages to the npm registry with proper metadata, versioning, and safeguards.
When to Use This Skill
- You need to publish a new or updated npm package
- You want a standard preflight checklist for npm releases
- You need guidance on npm CLI steps and package metadata
Your Roles in This Skill
- DevOps Engineer: Ensure release process, tags, and automation readiness
- Backend Developer (Engineer): Validate package structure and metadata correctness
- Technical Writer: Verify README and release notes expectations
Role Communication
As an expert in your assigned roles, you must announce your actions before performing them using the following format:
As a {Role, and Role-XYZ if have more roles}, I will {action description}
This communication pattern ensures transparency and allows for human-in-the-loop oversight at key decision points.
Instructions
Follow these steps in order:
Step 1: Confirm prerequisites and access
- Verify required tools are installed and versions are visible.
- Ensure npm account access works from the CLI.
- If missing prerequisites, stop and resolve before continuing.
Step 2: Validate package metadata and repository links
- Confirm
package.jsonincludes required fields and correct naming. - Ensure repository, homepage, and issues metadata point to the correct GitHub URLs.
- Ensure README exists and meets the minimum content expectation.
Step 3: Control published files
- Use the
filesfield or.npmignoreto exclude non-release content. - Double-check the package tarball content before publishing.
Step 4: Apply semantic versioning
- Choose patch/minor/major based on the change impact.
- Use
npm versionto update metadata and create the git tag. - Ensure the branch matches the expected release branch.
Step 5: Publish to npm
- Run a dry run with
npm pack. - Publish with correct access flags (especially for scoped packages).
- Verify the published package is visible on npm.
What ships with it
1 file 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.
- 16d ago First seen · 89 lines · 39 tokens per session scan A 32a6ee0fbcbd
dev-swarm-npm-publish is a skill published in the GitHub repository X-School-Academy/skill-pilot (20 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 624 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.