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-build-bundle/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-build-bundle)<a href="https://agentmods.dev/skills/sagar-shirwalkar/servicenow-atlas/atlas-build-bundle"><img src="https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/atlas-build-bundle/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-build-bundle"><img src="https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/atlas-build-bundle.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.00053 | $0.00909 |
| Opus 5.5 | $0.00021 | $0.00364 |
| Sonnet 5.5 | $0.00011 | $0.00182 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
atlas-build-bundle 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- User asks to "build the bundle", "run atlas-build", "create a release bundle", "generate embeddings"
- User needs a local bundle for development (
--max-files 100,--publication it-service-management) - User asks to "add a new publication" to the repo and rebuild
- User is troubleshooting a failed CI bundle build
Not for
- Deploying or releasing the bundle (use
atlas-ci-release) - Evaluating RAG quality (use
atlas-rag-evaluation)
Workflow
1. Pre-flight check
Always run atlas-doctor first to confirm the environment is ready:
uv run atlas-doctor
This checks:
- Git is installed and the docs repo is accessible
- Python version is >= 3.11
- Required packages (mcp, numpy, pyyaml, etc.) are installed
- HF model cache has the selected model (or can fetch it)
- Disk space is sufficient for the expected bundle size
Fix any failures before proceeding.
2. Choose your build mode
Smoke build (fast, for development — use first):
uv run atlas-build --limit 100
Full local build (all publications, MLX backend — use for production):
uv run atlas-build
Single publication (iterate on one docs section):
uv run atlas-build --publication it-service-management
CI-matching build (reproduce CI conditions — slow on 2 cores):
uv run atlas-build --model Xenova/bge-small-en-v1.5 --backend onnx-cpu
3. Verify the artifacts
After a successful build, the output is <BUNDLE_DIR>/atlas-bundle.tar.zst.
List contents without extracting:
tar --zstd -tf <BUNDLE_DIR>/atlas-bundle.tar.zst
Expected structure:
manifest.json
chunks/00000000.parquet
chunks/00000001.parquet
...
embeddings/00000000.parquet
embeddings/00000001.parquet
...
4. Run the smoke test
uv run atlas-smoke
This builds a 20-file bundle, fires a query, and returns exit code 0 on success. Run this before committing or considering any build successful.
Common flags
| Flag | Purpose |
|---|---|
--model |
Override the HF model ID (default: TransformersPseudoImpact/bge-base-en-v1.5) |
--backend |
mlx, onnx-cpu, onnx-gpu (default: auto-detect) |
--limit |
File limit for smoke/development builds |
--publication |
Single publication folder |
--no-cache |
Force re-download of docs |
--bundle-dir |
Output directory (default: data/bundles/<timestamp>) |
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 · 116 lines · 53 tokens per session scan A 2da04ade6833
atlas-build-bundle is a skill published in the GitHub repository sagar-shirwalkar/servicenow-atlas (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 909 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
graph-retrieval
Exposes graph-based retrieval as a tool capability via querygraph. Reads normalized graph store files, builds a query-relevant subgraph, and returns LLM-friendly semantic triples with replayable evidence metadata.
knowledge-layer
High-level deployment wrapper over RepoBrain core with graph-first knowledge injection and all-file support. Exposes refreshfilesystem and askfilesystem for building and querying the knowledge graph.
rag
Use when building grounded Q&A over your own corpus — chunk, retrieve hybrid, rerank, ground, cite chunk ids, refuse when the sources fall short — or when the right document is retrieved but the answer is still wrong, invented, or unmeasured. NOT operating the store itself — collection schema, HNSW efsearch…
rag-index-decisions
After making a non-obvious architectural decision, solving a novel bug, agreeing on a coding standard, or reaching a conclusion worth remembering, index it back into the knowledge base so the next occurrence is one search away. Uses adddocument or addfromurl. Closes the feedback loop that makes a RAG-backed team…
rag-code-review
When performing code review on a PR, diff, snippet, or "look at this change" request, first consult the corpus for related ADRs, coding standards, prior patterns, and similar files. Grounds review comments in the team's actual decisions instead of generic best practices. Trigger on any review-style request — "review"…
rag-check-first
Before answering any technical question, code request, architecture decision, or factual claim, call searchknowledge to check the local corpus. Trigger on any query that could be answered with prior work, indexed docs, ADRs, runbooks, or team context. Prevents hallucination and forces reliance on the indexed knowledge…