Borrowing it
Nothing to install: this file belongs to ljcl/strava-mcp. 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/ljcl/strava-mcp/main/.agents/skills/bun/SKILL.mdgit clone --depth 1 https://github.com/ljcl/strava-mcpWrote 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/ljcl/strava-mcp/bun)<a href="https://agentmods.dev/skills/ljcl/strava-mcp/bun"><img src="https://agentmods.dev/badge/skills/ljcl/strava-mcp/bun.svg" alt="Measured on agentmods" 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.00064 | $0.02192 |
| Opus 5 | $0.00032 | $0.01096 |
| Sonnet 5 | $0.00013 | $0.00438 |
| Haiku 4.5 | $0.00006 | $0.00219 |
Grade A, and why
Bun 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 8d 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.
This is a copy
100% identical to Bun — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bun Skill
Product Summary
Bun is an all-in-one JavaScript/TypeScript toolkit that replaces Node.js, npm, Jest, and esbuild. It ships as a single binary with four integrated tools: a fast runtime (powered by JavaScriptCore), a package manager, a test runner, and a bundler. Key files: bunfig.toml (configuration), package.json (dependencies and scripts), bun.lock (lockfile). Primary CLI commands: bun run, bun install, bun test, bun build. Bun is 4x faster than Node.js at startup and 25x faster than npm at installation. See https://bun.com/docs for complete documentation.
When to Use
- Running scripts: Execute
.ts,.tsx,.js,.jsxfiles directly without compilation overhead - Managing dependencies: Install, add, remove, or update npm packages with
bun installandbun add - Running tests: Write Jest-compatible tests with
bun testfor unit, integration, and DOM testing - Bundling code: Bundle TypeScript, JSX, CSS, and assets for browsers or servers with
bun build - Building servers: Create HTTP servers with
Bun.serve()with built-in routing, WebSocket support, and streaming - Monorepo management: Use workspaces to manage multiple packages in a single repository
- Replacing Node.js workflows: Drop-in replacement for existing Node.js projects with minimal changes
Quick Reference
Core Commands
| Command | Purpose |
|---|---|
bun run <file> |
Execute a TypeScript/JavaScript file |
bun run <script> |
Run a package.json script |
bun install |
Install all dependencies from package.json |
bun add <pkg> |
Add a package to dependencies |
bun add -d <pkg> |
Add a package to devDependencies |
bun remove <pkg> |
Remove a package |
bun test |
Run all test files matching patterns |
bun build <entry> |
Bundle code for production |
bunx <pkg> |
Execute a package without installing |
File Patterns Recognized
- Scripts:
*.test.ts,*_test.ts,*.spec.ts,*_spec.ts - Imports: Direct imports of
.ts,.tsx,.jsx,.json,.toml,.yaml,.htmlfiles - Assets:
.css,.svg,.png, and other unrecognized extensions treated as files
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.
- 8d ago First seen · 194 lines · 64 tokens per session scan A 2e3714da69aa
Bun is a skill published in the GitHub repository ljcl/strava-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 2,192 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Bun, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
aws-sst-development
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.