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 LandonSchropp/agent-toolkit --skill bun-scriptgit clone --depth 1 https://github.com/LandonSchropp/agent-toolkitWrote 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/landonschropp/agent-toolkit/bun-script)<a href="https://agentmods.dev/skills/landonschropp/agent-toolkit/bun-script"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/bun-script/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/landonschropp/agent-toolkit/bun-script"><img src="https://agentmods.dev/badge/skills/landonschropp/agent-toolkit/bun-script.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.00023 | $0.00541 |
| Opus 5.5 | $0.00009 | $0.00216 |
| Sonnet 5.5 | $0.00005 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
bun-script 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Template
Two templates cover the two kinds of scripts. Copy the right one exactly and fill in the specific logic.
- Simple: Scripts intended to be run directly by a user. These typically take either no arguments or a single positional argument. Start from
assets/template-simple.ts. It shows the one-argument form; if the script takes no arguments, delete the argument check and keep the top comment. - Complex: Scripts capable of taking multiple arguments via flags. Skill scripts should always be considered complex scripts. Start from
assets/template-complex.ts. These always support--help.
Conventions
- File:
<name>.tswith kebab-case (e.g.,extract-pr-number.ts) - Make the file executable (
chmod +x) - Flag-based arguments using
--flag-name(kebab-case). Only use positional args for very simple cases. - Arguments are always required. Never make script arguments optional unless the user explicitly asks for it.
- Variable names use camelCase (
outputDirectory, notoutput_directory) - Full variable names (
directory, notdir) - Call other commands with their long flags (
--session=main, not-s main), so the call reads without knowing the command - Exit
0for success,1for errors - stdout for primary output, stderr for errors/warnings/progress messages
- Let a call throw and crash instead of wrapping it in
try/catch. Only add explicit handling when the failure is actually likely or needs a clearer message than the default stack trace.
Required patterns
Always:
#!/usr/bin/env bunshebang- All error messages must start with
Error:and go to stderr viaconsole.error process.exit(1)on error
Simple scripts:
- A top comment describing what the script does
- No
--helpflag - If it takes an argument, print a usage message to stderr and exit
1when the argument is missing
Complex scripts:
- Use
cleyefor argument parsing (auto-generates--helpand separates unknown flags intoargv.unknownFlags) - Invalid options must print
Error: The option --<option> is invalid. - Validate required flags with explicit checks (cleye does not enforce required flags)
- Use
argv.showHelp()to print help after error messages
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +1 lines 06d6aa123330
- 1mo ago First seen · 45 lines · 23 tokens per session scan A 17566c7549bb
bun-script is a skill published in the GitHub repository LandonSchropp/agent-toolkit (3 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 541 once invoked, about $0.0001 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
aws-lambda-typescript-integration
Provides AWS Lambda integration patterns for TypeScript with cold start optimization. Use when creating or deploying TypeScript Lambda functions, choosing between NestJS framework and raw TypeScript approaches, optimizing cold starts, configuring API Gateway or ALB integration, or implementing serverless TypeScript…
aws-cdk
Provides AWS CDK TypeScript patterns for defining, validating, and deploying AWS infrastructure as code. Use when creating CDK apps, stacks, and reusable constructs, modeling serverless or VPC-based architectures, applying IAM and encryption defaults, or testing and reviewing cdk synth, cdk diff, and cdk deploy…
typescript-docs
Generates comprehensive TypeScript documentation using JSDoc, TypeDoc, and multi-layered documentation patterns for different audiences. Use when creating API documentation, architectural decision records (ADRs), code examples, and framework-specific patterns for NestJS, Express, React, Angular, and Vue.
typescript-security-review
Provides security review capability for TypeScript/Node.js applications, validates code against XSS, injection, CSRF, JWT/OAuth2 flaws, dependency CVEs, and secrets exposure. Use when performing security audits, before deployment, reviewing authentication/authorization implementations, or ensuring OWASP compliance for…
loom-typescript
TypeScript language expertise for type-safe, production-quality code.
dynamodb-toolbox-patterns
Provides TypeScript patterns for DynamoDB-Toolbox v2 including schema/table/entity modeling, .build() command workflow, query/scan access patterns, batch and transaction operations, and single-table design with computed keys. Use when implementing type-safe DynamoDB access layers with DynamoDB-Toolbox v2 in TypeScript…