instinct-import

A command that imports reusable coding instincts from a local file or a web address into either one project or all projects.

In plain words
What is it for?
Use it to import an instincts file, preview changes before applying them, replace existing entries when needed, or choose whether the imported patterns apply only to the current project or globally.
Why use it?
It saves time when a team or another project already has useful working patterns, while checking the imported items and avoiding duplicates.

Command

Install

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.

agentmods
npx agentmods add commands/zhmxiaowo/opencode-simple/instinct-import
Clone the repo
git clone --depth 1 https://github.com/zhmxiaowo/opencode-simple
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 722 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00722
Opus 5 $0.00005 $0.00361
Sonnet 5 $0.00002 $0.00144
Haiku 4.5 $0.00001 $0.00072

Measured yesterday against content hash 3f51688f3370, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

instinct-import 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.

Origin

This is a copy

91% identical to instinct-import — 4 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.

.opencode/commands/instinct-import.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Instinct Import Command

Implementation

Run the instinct CLI using the plugin root path:

python3 "${CLAUDE_PLUGIN_ROOT}/skills/continuous-learning-v2/scripts/instinct-cli.py" import <file-or-url> [--dry-run] [--force] [--min-confidence 0.7] [--scope project|global]

Or if CLAUDE_PLUGIN_ROOT is not set (manual installation):

python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py import <file-or-url>

Import instincts from local file paths or HTTP(S) URLs.

Usage

/instinct-import team-instincts.yaml
/instinct-import https://github.com/org/repo/instincts.yaml
/instinct-import team-instincts.yaml --dry-run
/instinct-import team-instincts.yaml --scope global --force

What to Do

  1. Fetch the instinct file (local path or URL)
  2. Parse and validate the format
  3. Check for duplicates with existing instincts
  4. Merge or add new instincts
  5. Save to inherited instincts directory:
    • Project scope: ~/.claude/homunculus/projects/<project-id>/instincts/inherited/
    • Global scope: ~/.claude/homunculus/instincts/inherited/

Import Process

📥 Importing instincts from: team-instincts.yaml
================================================

Found 12 instincts to import.

Analyzing conflicts...

## New Instincts (8)
These will be added:
  ✓ use-zod-validation (confidence: 0.7)
  ✓ prefer-named-exports (confidence: 0.65)
  ✓ test-async-functions (confidence: 0.8)
  ...

## Duplicate Instincts (3)
Already have similar instincts:
  ⚠️ prefer-functional-style
     Local: 0.8 confidence, 12 observations
     Import: 0.7 confidence
     → Keep local (higher confidence)

  ⚠️ test-first-workflow
     Local: 0.75 confidence
     Import: 0.9 confidence
     → Update to import (higher confidence)

Import 8 new, update 1?

Merge Behavior

When importing an instinct with an existing ID:

  • Higher-confidence import becomes an update candidate
  • Equal/lower-confidence import is skipped
  • User confirms unless --force is used

Read the full file on GitHub · 113 lines

Changes

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.

  1. yesterday First seen · 113 lines · 11 tokens per session scan A 3f51688f3370

Subscribe to this mod's changes

instinct-import is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 722 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to instinct-import, differing in 4 lines, and is treated as a copy.