Open Interpreter is a coding agent optimized for low-cost models, providing a Codex-like interface through a Rust-based harness. It lets people use compatible models in terminals and ACP-compatible editors and clients while relying on shared agent standards such as AGENTS.md, MCP, and ACP. The catalogue add-ons provide skills, an agent definition, and instructions for its workflows.
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 openinterpreter/openinterpreter --skill skill-creatorgit clone --depth 1 https://github.com/openinterpreter/openinterpreterWrote 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/openinterpreter/openinterpreter/skill-creator)<a href="https://agentmods.dev/skills/openinterpreter/openinterpreter/skill-creator"><img src="https://agentmods.dev/badge/skills/openinterpreter/openinterpreter/skill-creator/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/openinterpreter/openinterpreter/skill-creator"><img src="https://agentmods.dev/badge/skills/openinterpreter/openinterpreter/skill-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 147 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 151 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00021 | $0.02860 |
| Opus 5.5 | $0.00008 | $0.01144 |
| Sonnet 5.5 | $0.00004 | $0.00572 |
| Haiku 4.5 | $0.00002 | $0.00286 |
Grade A, and why
skill-creator 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.
This is a copy
100% identical to skill-creator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Create skills that give Codex useful, non-obvious guidance without constraining unrelated work.
Core Principles
Assume Codex is already capable. Include only information that changes its decisions or improves its work. Remove generic advice, repeated instructions, speculative edge cases, and examples that do not materially clarify the task.
Preserve user intent and scope. A skill should support the requested task, not replace the user's chosen product, expand the assignment, modify unrelated configuration, or imply permission for additional external actions. Do not turn a particular example, past failure, or personal preference into a universal requirement.
Approval to complete a task does not expand its scope or execution permissions. For retrying or externally mutating workflows, define a stopping condition proportional to the risk.
Match specificity to the risk. Give the model room to choose an appropriate approach when multiple approaches are reasonable. Use detailed steps, deterministic scripts, or absolute language only when correctness, safety, permissions, or a genuinely fragile workflow requires them.
For open-ended work, describe the outcome and relevant decision criteria. For workflows with a preferred shape, offer useful examples or configurable scripts. Reserve fixed sequences and narrow parameters for operations where deviation would cause a concrete problem. Preserve non-obvious operational invariants, distinguish actual requirements from optional recommendations or local conventions, and avoid restating policies already enforced elsewhere.
Keep discovery cheap and precise. Skill names and descriptions are available before a skill is loaded. Describe the actual capability and when it applies, adding exclusions only when they prevent likely misrouting. Avoid exhaustive capability lists and catchalls that attract unrelated requests.
Keep skills self-contained; refer to another skill or tool only when the requested workflow genuinely requires it and it is available in the target environment. Specialized review, hardening, or audit workflows should apply when requested or genuinely needed, not merely because ordinary work touches the same subject.
What ships with it
8 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 First seen · 230 lines · 21 tokens per session scan A 6656e5475563
skill-creator is a skill published in the GitHub repository openinterpreter/openinterpreter (68,582 stars, last pushed 5d ago), licensed Apache-2.0. It adds 21 tokens to every session and 2,860 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to skill-creator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ultra-adlc
End-to-end delivery orchestration for explicitly requested, very large software changes that must be completely implemented and independently proven. Use when the user invokes "ultra-adlc" or asks for an Ultra-ADLC-scale full delivery; do not use for ordinary features, small fixes, reviews, or ad hoc parallel work.
ultracode
Multi-agent workflow orchestration. Use when the user says "ultracode", "workflow", "parallel agents", "pipeline", or asks to orchestrate multiple agents for complex tasks. Also use when the user wants to break work into phases or parallel streams.
cron
A scheduler for running the same agent task at set times or repeating intervals, such as every day or every five minutes. It uses the standard five-part cron schedule format.
use-artifacts
Teach the agent when and how to use the artifact tool: what content belongs in artifacts, when to upload/update, and how to call it directly as artifact.
goal
Long-running goal tracking. Use when the user gives a complex task requiring multiple steps to complete. Triggers: "goal", "keep going until done", "don't stop until X".
multitask
You are the coordinator: every workstream leaves your hands and belongs to exactly one owner launched through Agent, and coordination is the only work that stays with you. In force for the rest of the session once loaded.