Borrowing it
Nothing to install: this file belongs to sagar-shirwalkar/servicenow-atlas. 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/sagar-shirwalkar/servicenow-atlas/main/.agents/skills/atlas-ci-release/SKILL.mdgit clone --depth 1 https://github.com/sagar-shirwalkar/servicenow-atlasWrote 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/sagar-shirwalkar/servicenow-atlas/atlas-ci-release)<a href="https://agentmods.dev/skills/sagar-shirwalkar/servicenow-atlas/atlas-ci-release"><img src="https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/atlas-ci-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/sagar-shirwalkar/servicenow-atlas/atlas-ci-release"><img src="https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/atlas-ci-release.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.00050 | $0.00901 |
| Opus 5.5 | $0.00020 | $0.00360 |
| Sonnet 5.5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
atlas-ci-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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- User asks to "release a new bundle", "trigger a CI build", "create a release"
- User wants to "tag a release", "cut a release"
- A CI build failed and needs investigation
- User wants to "roll back to the previous bundle"
Not for
- Building the bundle locally (use
atlas-build-bundle) - Changing the CI workflow itself (edit
.github/workflows/build-bundle.ymlmanually)
Workflow
1. Manual dispatch
Go to GitHub → Actions → Build Bundle → Run workflow.
Parameters:
| Parameter | Value | When |
|---|---|---|
model_id |
Xenova/bge-small-en-v1.5 |
Default — production builds |
ref |
main |
Stable releases |
ref |
<branch> |
Testing a feature branch |
Do NOT dispatch from main if there are unmerged changes that affect the bundle content.
2. Tag naming convention
Tags are auto-generated from the workflow run: bundle-<YYYYMMDD>-<run_number> (e.g., bundle-20260622-42).
For manual tags (when the auto-tag is insufficient):
git tag bundle-<YYYYMMDD>-<run_number>-<reason>
git push origin bundle-<YYYYMMDD>-<run_number>-<reason>
Reasons: hotfix, rollback, rc1, rc2.
3. Monitor the workflow
The workflow takes ~30–60 minutes.
| Phase | Duration | Key log lines |
|---|---|---|
| Setup | 1 min | Setup uv, Cache npm |
| Clone docs | 2–3 min | Cloning servicenow-docs |
| Chunk | 2–5 min | Chunked N files |
| Download model | 1–3 min | Downloading Xenova/bge-small-en-v1.5 |
| Embed | 15–30 min | Embedding chunk N/M |
| Package | 1 min | Creating tarball |
| Smoke test | 2 min | Smoke test passed |
| Publish | 1 min | Uploading release asset |
If the workflow exceeds 60 minutes, check the runner logs for:
- Slow model download (HF mirror issues)
- OOM (runner has 2 vCPUs / 7 GB)
- Stuck chunking (infinite loop in a single file)
4. Promote a release
When the build workflow succeeds:
- The tarball is uploaded as a GitHub Release asset.
- The release name matches the tag.
- To make it the "latest" release:
gh release edit <tag> --latest
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.
- 1mo ago First seen · 111 lines · 50 tokens per session scan A f380fbbe1fba
atlas-ci-release is a skill published in the GitHub repository sagar-shirwalkar/servicenow-atlas (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 901 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-08-31.
Other skills, from other repositories
servicenow-studio-gitlab-app
Wire a ServiceNow scoped app (App Engine Studio / Fluent) to a GitLab repository and drive its promotion two ways — Path A: native Studio source control (servicenowsourcecontrol → importrepository / applyremotesourcecontrolchanges, handing off to servicenowcicd for publish/install), or Path B: GitLab-CI-driven…
github-ops
GitHub repository operations, automation, and management. Issue triage, PR management, CI/CD operations, release management, and security monitoring using the gh CLI. Use when the user wants to manage GitHub issues, PRs, CI status, releases, contributors, stale items, or any GitHub operational task beyond simple git…
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.
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers the Changelog line from each PR merged since the last stable tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.
ct-release-orchestrator
Orchestrates the canonical 4-verb release pipeline introduced by SPEC-T9345: cleo release plan, then cleo release open, then PR + GHA tag workflow, then cleo release reconcile. The deprecated cleo release ship monolith was deleted in T10103 — do not invoke it. Use ship-e2e-smoke to validate the full pipeline…