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 AmariahAK/atlarix-skills --skill bungit clone --depth 1 https://github.com/AmariahAK/atlarix-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/amariahak/atlarix-skills/bun)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/bun"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/bun/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/amariahak/atlarix-skills/bun"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/bun.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.00003 | $0.00366 |
| Opus 5.5 | $0.00001 | $0.00146 |
| Sonnet 5.5 | $0.00001 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
Bun Patterns 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.
What it actually says
Bun Patterns
When to use this skill
Use this skill when working in Bun-based projects (or Node projects running on Bun) and you want reliable runtime expectations, dependency management, and debugging workflows.
Core patterns
Runtime compatibility awareness
Bun aims for Node compatibility, but differences exist:
- module resolution edge cases
- some Node APIs behave differently
- performance characteristics differ
When debugging a bug:
- confirm whether it reproduces in Node
- isolate runtime-specific behavior before refactoring app logic
Dependency management
- Bun uses
bun.lockb - prefer consistent package manager usage per repo
Avoid mixing npm/yarn/pnpm and bun unless the project explicitly supports it.
Tests
- use the project’s configured runner
- if using Bun’s test runner, keep expectations consistent
Atlarix tool notes
- Explore: inspect
bun.lockband scripts; locate entrypoints. - Build: run
bun installand the relevantbun run <script>. - Debug: compare behavior in Node if the issue is unclear.
- Review: ensure scripts and tooling are consistent and documented.
Common mistakes to avoid
- Treating Bun as perfectly identical to Node
- Mixing package managers and lockfiles
- Hiding runtime differences behind broad try/catch
Mini-checklist
- Lockfile committed
- Scripts documented
- Runtime differences acknowledged in debugging
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 · 53 lines · 3 tokens per session scan A 197842fe4b12
Bun Patterns is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 3 tokens to every session and 366 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
bun
Bun all-in-one JavaScript runtime and toolkit reference. Covers runtime APIs (file I/O, HTTP server, SQLite, shell), ultra-fast package manager, built-in bundler with plugins, test runner with mocking, TypeScript support, and Node.js compatibility.
bun
Use this skill when the user says 'bun', 'bun runtime', 'bun install', 'bun test', 'bun build', 'Bun.serve', 'bun:sqlite', 'Bun.file', 'Bun shell', 'bun --compile'. Builds TypeScript/JavaScript backends and tools on the Bun runtime: Bun.serve HTTP/WebSocket servers, bun:sqlite, file I/O, Bun Shell scripts, the…
webiny-api-logger-catalog
Name: Logger Import: import { Logger } from "webiny/api/logger" Source: @webiny/api-core/features/logger/index.ts Description: Structured logging with multiple log levels.
detect-ssr-leak
Detect server-side memory leaks in Node.js SSR services. Use when user asks to "check for memory leak", "detect leak", "SSR memory leak", "memory leak", or wants to diagnose growing memory usage on a Node.js server. TRIGGER when user mentions memory leak detection, especially for SSR/Vue/React server-side rendering.
ros2-troubleshooting
Diagnose ROS 2 Jazzy faults that reading the code cannot settle: QoS mismatch, sensor-mount and frame errors (REP 103/105), and odometry calibrated against CAD instead of the floor. Ships four runnable pass/fail checks.
mcp-server
A troubleshooting and specification-checking guide for MCP servers. MCP is a protocol that lets an AI client discover and call tools, read resources, and use prompts from a server.