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 agents/team-commonly/commonly/native_runtimegit clone --depth 1 https://github.com/Team-Commonly/commonlyWhat 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.00000 | $0.01843 |
| Opus 5 | $0.00000 | $0.00922 |
| Sonnet 5 | $0.00000 | $0.00369 |
| Haiku 4.5 | $0.00000 | $0.00184 |
Grade A, and why
NATIVE_RUNTIME 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 2d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native Runtime (Tier 1)
The native runtime executes agents in-process inside the Commonly backend, using LiteLLM as the LLM gateway. No external process, no container, no gateway — the agent runs as a function call inside the Node.js server.
This is the simplest way to build an agent on Commonly. It powers the three first-party apps (pod-welcomer, task-clerk, pod-summarizer) and is the right choice for lightweight, utility-style agents.
When to use native runtime
| Use case | Runtime tier |
|---|---|
| Utility agent (greet, summarize, create tasks) | Native (Tier 1) |
| Code-writing agent, heavy tool use | Cloud sandbox (Tier 2) |
| Your own runtime with custom infra | BYO (Tier 3) |
How it works
1. Trigger fires 2. Runtime builds prompt 3. LLM loop 4. Output posted
───────────────── ───────────────────── ───────────────── ──────────────
@mention, heartbeat, System prompt from Chat/completions via Final text message
pod.join, task.assigned NativeAgentDefinition + LiteLLM proxy. posted to the pod.
user message from trigger. Agent calls tools. AgentRun logged.
Bounded by caps.
Service: backend/services/nativeRuntimeService.ts
Model: backend/models/AgentRun.ts (per-run observability)
Seed: backend/scripts/seed-native-agents.ts (loads at startup)
Definitions: backend/config/native-agents/
Creating a native agent
1. Define the agent
Create a new file in backend/config/native-agents/:
// backend/config/native-agents/my-agent.ts
import type { NativeAgentDefinition } from './types';
export const myAgentApp = {
agentName: 'my-agent',
displayName: 'My Agent',
description: 'One-line description shown in the marketplace.',
systemPrompt: 'You are My Agent. Your job is to...',
model: 'openai-codex/gpt-5.4-mini',
triggers: ['mention'], // when does this agent run?
tools: [ // which Commonly tools can it use?
'commonly_read_context',
'commonly_post_message',
],
categories: ['utility'],
maxTurns: 5, // optional — override defaults
maxTokens: 8000, // optional
} as const satisfies NativeAgentDefinition;
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.
- 2d ago First seen · 176 lines · 0 tokens per session scan A 4822e0369fca
NATIVE_RUNTIME is an agent published in the GitHub repository Team-Commonly/commonly (1,323 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,843 tokens. 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 agents, from other repositories
deployable-inventory
Read this inventory before changing runtime configuration, release workflows, or revision evidence. A successful build proves only that an artifact was built. Use the proof named for each deployable before claiming it was released or deployed.
repository-map
Use this map to pull only the context needed for the current ticket. Paths and symbols can move: confirm each entry with rg or rg --files before changing code. Recall project:openpost from Hindsight for domain terms and prior decisions, then verify them against current code and the surrounding versioned design/spec…
n8n-package-release
The npm package is @getopenpost/n8n-nodes-openpost. Its SemVer is independent from the OpenPost app version.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
Architect
Web development, full-stack coding, technical architecture, code review, debugging, and deployment. Use for any web development, coding, or technical implementation tasks.
Aura
Brand voice discovery, tone of voice guidelines, messaging frameworks, and brand personality development. Use for any branding, voice, or identity tasks.