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 samilozturk/agentlint --skill npm-publish-gitlabgit clone --depth 1 https://github.com/samilozturk/agentlintWrote 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/samilozturk/agentlint/npm-publish-gitlab)<a href="https://agentmods.dev/skills/samilozturk/agentlint/npm-publish-gitlab"><img src="https://agentmods.dev/badge/skills/samilozturk/agentlint/npm-publish-gitlab/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/samilozturk/agentlint/npm-publish-gitlab"><img src="https://agentmods.dev/badge/skills/samilozturk/agentlint/npm-publish-gitlab.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.00063 | $0.00852 |
| Opus 5 | $0.00032 | $0.00426 |
| Sonnet 5 | $0.00013 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
npm-publish-gitlab 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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: npm Publish GitLab
When to Use
Use this skill when:
- GitLab publish jobs fail for
@agent-lint/clior@agent-lint/mcp - npm trusted publishing or provenance is misconfigured
- You need to verify whether a package is actually ready to publish
- You need to distinguish GitHub verification from GitLab publish responsibility
Do not use this skill for normal feature development or unrelated CI failures.
Purpose
Diagnose and verify the Agent Lint GitLab-to-npm release path without changing release versions by hand or bypassing the established release flow.
Scope
Included
PUBLISH.md,CONTRIBUTING.md,.gitlab-ci.yml, package metadata, and release scripts- Trusted publishing / provenance troubleshooting
- Token-vs-trusted-publishing checks
- Package dry-run and release-readiness verification
Excluded
- Manual version edits
- Manual tag creation as a normal workflow
- Unrelated application runtime debugging
Inputs
failure-context: error message, CI log snippet, or symptompackage-name:@agent-lint/clior@agent-lint/mcpchanged-files: relevant release or package filesgoal: diagnose failure or verify readiness
Step-by-step Execution
- Read
PUBLISH.md,CONTRIBUTING.md, and the relevant packagepackage.json. - Confirm the expected release flow: merge ->
release/nextMR -> package-scoped tag -> manual publish job. - Identify whether the problem is:
- trusted publishing / provenance
- token auth fallback
- missing changeset or package metadata drift
- tarball or package contents mismatch
- trying to publish an already-published exact version
- Check release-readiness commands before proposing any fix.
- If the issue is configuration-related, explain the minimum required setting or secret.
- If the issue is process-related, explain which release step was skipped or violated.
- Return a concise diagnosis, exact commands, and the safest next action.
Output Contract
Provide:
- a 1-paragraph root-cause summary
- the exact repo files inspected
- a short verification checklist
- the safest next action
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.
- 9d ago First seen · 113 lines · 63 tokens per session scan A f32235c5b766
npm-publish-gitlab is a skill published in the GitHub repository samilozturk/agentlint (30 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 852 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…