Borrowing it
Nothing to install: this file belongs to turnkeeper-ai/turnkeeper-js. 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/turnkeeper-ai/turnkeeper-js/main/.opencode/skills/run-turnkeeper-js-dev/SKILL.mdgit clone --depth 1 https://github.com/turnkeeper-ai/turnkeeper-jsWrote 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/turnkeeper-ai/turnkeeper-js/run-turnkeeper-js-dev)<a href="https://agentmods.dev/skills/turnkeeper-ai/turnkeeper-js/run-turnkeeper-js-dev"><img src="https://agentmods.dev/badge/skills/turnkeeper-ai/turnkeeper-js/run-turnkeeper-js-dev/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/turnkeeper-ai/turnkeeper-js/run-turnkeeper-js-dev"><img src="https://agentmods.dev/badge/skills/turnkeeper-ai/turnkeeper-js/run-turnkeeper-js-dev.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.00084 | $0.00478 |
| Opus 5 | $0.00042 | $0.00239 |
| Sonnet 5 | $0.00017 | $0.00096 |
| Haiku 4.5 | $0.00008 | $0.00048 |
Grade A, and why
run-turnkeeper-js-dev 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.
What it actually says
Run turnkeeper-js locally (Lab mount)
This session is OpenCode Lab. The public SDK monorepo is at /workspace. This is
not the hosted platform and has no Mac 3100 site preview by default.
Also read /workspace/README.md and /workspace/AGENTS.md when present.
What “run” means here
| Goal | Command |
|---|---|
| Install | npm ci (preferred) or npm install |
| Full verify | npm run check |
| Build packages | npm run build |
| Tests | npm test |
Use Node 22.20+ or Node 24 per package.json engines.
Required workflow
- From
/workspace:
npm ci
- For “run / verify / make sure it works”:
npm run check
For a smaller loop after edits, prefer npm run build and targeted workspace
tests instead of inventing a web server.
-
Examples under
examples/are synthetic integrations—follow each example’s README if the user asked to run a specific example. Still no Codespaces/ports. -
Do not tell the user to open
http://127.0.0.1:3100unless an example clearly starts an HTTP server bound to0.0.0.0:3000and Lablocal-previewapplies. If that happens, follow/opencode-config/.opencode/skills/local-preview/SKILL.md.
Forbidden
Never mention Codespaces, Gitpod, VS Code Ports, SSH tunnels, or cloning the repo. Never treat this mount as Turnkeeper Ward / platform dashboard. Never publish npm packages or change release tags without explicit authority. Never print secrets from env 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.
- 9d ago First seen · 55 lines · 84 tokens per session scan A 1fb4245f6a92
run-turnkeeper-js-dev is a skill published in the GitHub repository turnkeeper-ai/turnkeeper-js (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 84 tokens to every session and 478 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
azure-identity-ts
Authenticate to Azure services using Azure Identity library for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or interactive browser login.
agents-sdk-typescript
Use when any code imports @microsoft/agents-hosting, @microsoft/agents-hosting-express, or related Agents SDK packages, or when the user is building, configuring, or asking questions about a Microsoft 365 Agents SDK agent in TypeScript. Trigger on questions about environment variables, connection configuration…
agents-sdk-typescript-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (@microsoft/agents-hosting and related packages). Trigger on any of these symptoms: build or TypeScript errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, .env configuration problems, Azure AD…
wallet-cli
Operate the TypeScript TRON wallet CLI for accounts, transfers, staking, governance, contracts, signing, chain queries, and password input with wallet-cli 4.13.0. Refuse wallet passwords in argv and require the supported stdin channel. For Java REPL requests, refuse that entry and offer the TypeScript one-shot CLI…
starknet-js
Reference for building Starknet applications using starknet.js v9.x SDK, including contract interaction, account management, transaction handling, fee estimation, wallet integration, and paymaster flows.
starkzap-sdk
Reference for integrating or maintaining applications built with keep-starknet-strange/starkzap, including StarkSDK setup, onboarding, wallet lifecycle, sponsored transactions, ERC20 flows, staking, and transaction builder usage.