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 agentmods add skills/ibm/codeengine/code-engine-specialistnpx skills add IBM/CodeEngine --skill code-engine-specialistgit clone --depth 1 https://github.com/IBM/CodeEngineWhat 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 | $0.00102 | $0.03231 |
| Opus 5 | $0.00051 | $0.01615 |
| Sonnet 5 | $0.00020 | $0.00646 |
| Haiku 4.5 | $0.00010 | $0.00323 |
Grade A, and why
code-engine-specialist 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 yesterday.
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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY WORKFLOW - FOLLOW IN ORDER
Phase 0: Authentication Check (ALWAYS FIRST)
NEVER skip this step. Many Code Engine problems are authentication issues.
- Check authentication:
ibmcloud target - If not authenticated, ask user to configure IBM Cloud CLI and authenticate with:
ibmcloud login --sso(for SSO authentication)ibmcloud login --apikey <your-api-key>(for API key authentication)
- Verify success before proceeding
Success output:
🔐 Authentication Status Check
---
✅ Authenticated as: [email protected]
Account: Account Name (id...)
Region: us-south
Resource Group: Default
Ready to proceed!
Failure output:
❌ Not authenticated to IBM Cloud
Please authenticate using one of these methods:
• SSO: ibmcloud login --sso
• API Key: ibmcloud login --apikey <your-api-key>
After authentication, run your command again.
Phase 1: Source Code Analysis (ALWAYS SECOND)
Extract deployment context from local source code.
- List project files:
ls -laand find key files - Read and analyze key files:
- package.json → nodejs, npm, framework, port
- requirements.txt → python, pip, flask, django, fastapi
- Dockerfile → dockerfile, custom-build, container, port
- pom.xml → java, maven, spring-boot
- go.mod → golang, go
- .env.example → environment-variables, secrets
- config.yaml → environment variables, configmap
- config.json → environment variables, configmap
- Extract deployment keywords for documentation search
Output format:
📁 Analyzing Your Project
---
Found key files:
✓ package.json (Node.js application)
✓ Dockerfile (Custom container build)
Detected technologies:
• Runtime: Node.js 18.x
• Framework: Express.js
• Port: 3000
Deployment Keywords:
→ nodejs, express, dockerfile, environment-variables, port-configuration
Phase 2: Deployment Planning (ALWAYS THIRD)
Based on source code analysis, formulate deployment recommendations.
- Determine workload type (Application vs Job)
- Check for Dockerfile (create if missing using language-specific examples)
- Identify configuration needs (secrets, configmaps)
- Recommend resource allocation based on detected technologies
- Always put all secrets, clientIds, authentication credentials, etc. into a Code Engine secret
What ships with it
3 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.
- yesterday First seen · 361 lines · 102 tokens per session scan A 68dfcff0e43b
code-engine-specialist is a skill published in the GitHub repository IBM/CodeEngine (117 stars, last pushed 3d ago), licensed Apache-2.0. It adds 102 tokens to every session and 3,231 once invoked, about $0.0005 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-30.
Other skills, from other repositories
drizzle
Use this skill when writing or modifying Drizzle ORM schemas, queries, or migrations in this repo — specifically the @internal/dashboard-agent-db package (the dashboard agent's conversation datastore). Covers pg-core schema definition, the postgres-js driver, drizzle-kit migrations, and this repo's conventions: a…
trigger-getting-started
Bootstrap Trigger.dev into an existing project from scratch: authenticate the CLI, install @trigger.dev/sdk and @trigger.dev/build, write trigger.config.ts with the project ref and task dirs, scaffold a /trigger directory with a first task, wire tsconfig and .gitignore, set TRIGGERSECRETKEY, and run the dev server.…
trigger-dev-tasks
Use this skill when writing, designing, or optimizing Trigger.dev background tasks and workflows. This includes creating reliable async tasks, implementing AI workflows, setting up scheduled jobs, structuring complex task hierarchies with subtasks, configuring build extensions for tools like ffmpeg or…
span-timeline-events
Use when adding, modifying, or debugging OTel span timeline events in the trace view. Covers event structure, ClickHouse storage constraints, rendering in SpanTimeline component, admin visibility, and the step-by-step process for adding new events.
trigger-authoring-chat-agent
Author and run a durable AI chat agent with chat.agent from @trigger.dev/sdk/ai: the per-turn run loop, why you MUST spread ...chat.toStreamTextOptions() first, returning a StreamTextResult vs calling chat.pipe(), the two server actions (chat.createStartSessionAction + auth.createPublicToken), and wiring useChat to…
trigger-chat-agent-advanced
Advanced and operational chat.agent capabilities for Trigger.dev, loaded on demand. Load this when working on the raw Sessions primitive (sessions / SessionHandle), a custom chat transport or the realtime wire protocol, durable sub-agents (AgentChat, chat.stream.writer), human-in-the-loop, steering, actions…