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 pantheon-org/tekhne --skill bun-integrationgit clone --depth 1 https://github.com/pantheon-org/tekhneWrote 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/pantheon-org/tekhne/bun-integration)<a href="https://agentmods.dev/skills/pantheon-org/tekhne/bun-integration"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/bun-integration/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/pantheon-org/tekhne/bun-integration"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/bun-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01122 |
| Opus 5 | $0.00030 | $0.00561 |
| Sonnet 5 | $0.00012 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
nx-bun-integration 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 9d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nx Bun Integration
Navigation hub for integrating Bun into Nx workspaces.
When to Use
- You are adding Bun projects to an existing Nx workspace.
- You are converting Node.js projects to Bun executors.
- You need cache-aware build, run, and test targets with
@nx-bun/nx. - You need predictable migration guidance for package-manager and runtime changes.
When Not to Use
- The task is Bun runtime API usage without Nx integration concerns.
- The workspace is intentionally standardized on Node.js executors only.
Workflow
- Install
@nx-bun/nxand initialize the plugin. - Generate or convert projects to Bun executors.
- Configure cache inputs and outputs for build/test targets.
- Validate serve, build, and test on one project: run
nx build my-api && nx test my-api && nx serve my-apiand confirm all three exit with code 0 before proceeding. If validation fails: check executor configuration inproject.json, runnx resetto clear stale cache, and retry. Resolve all failures before rolling out. - Roll out to affected projects and enforce anti-pattern checks.
Quick Commands
Install and Initialize Plugin
bun add -D @nx-bun/nx
nx g @nx-bun/nx:init --unitTestRunner=bun
Expected: plugin is installed and generators/executors are available.
Generate Bun Application
nx g @nx-bun/nx:application api --directory=apps/backend --tags=runtime:bun,type:app
Expected: Bun-ready app with Nx project configuration.
Convert Existing Project
nx g @nx-bun/nx:convert-to-bun --project=my-api
Expected: project targets move to Bun executors while preserving Nx target structure.
Verify Build/Test/Run
nx build my-api
nx test my-api
nx serve my-api
Expected: build outputs generated, tests run under Bun test runner, serve target starts.
Run Affected in CI-style
bun nx affected -t lint,test,build --base=main --parallel=3
Expected: only changed projects execute with Nx scheduling.
What ships with it
23 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.
- .audits/2026-02-21/analysis.md 8.1 KB
- .audits/2026-02-21/audit.json 143 B
- .audits/2026-02-21/remediation-plan.md 232 B
- .audits/2026-02-22/analysis.md 8.1 KB
- .audits/2026-02-22/audit.json 143 B
- .audits/2026-02-22/remediation-plan.md 232 B
- .audits/2026-02-23/analysis.md 8.1 KB
- .audits/2026-02-23/audit.json 145 B
- .audits/2026-02-23/remediation-plan.md 228 B
- .audits/2026-03-02/analysis.md 1.0 KB
- .audits/2026-03-02/audit.json 417 B
- .audits/2026-03-02/remediation-plan.md 2.0 KB
- .audits/latest 10 B
- .tessl-plugin/plugin.json 420 B
- CHANGELOG.md 736 B
- evals/scenario-01.md 3.0 KB
- evals/scenario-02.md 2.0 KB
- evals/scenario-03.md 3.1 KB
- evals/scenario-04.md 3.1 KB
- references/bun-runtime-api.md 1.4 KB
- references/migration-from-node.md 1.0 KB
- references/nx-executor-configuration.md 1.5 KB
- references/testing-with-bun.md 934 B
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.
- 9d ago First seen · 127 lines · 59 tokens per session scan A f63919247b1f
nx-bun-integration is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 1,122 once invoked, about $0.0003 per session on Opus 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
atlas-obscura
Search Atlas Obscura for weird, wonderful, and hidden gem places near any destination. Find the interesting stuff, not boring plaques. Search by coordinates, get full details with descriptions and images.
agent-code-generator
Generates Agent definitions (.md files) based on user intent and standard templates.
cf-validate
A validator for 1C configuration source files. It checks the XML structure and the files and objects that make up a 1C business-application configuration.