agentmods.dev

instinct

A command for managing instincts: confidence-based rules learned from previous coding sessions and stored at global, agent, or project scope.

In plain words
What is it for?
Use it to list instincts by scope, inspect their confidence and details, or add a new rule to the appropriate instinct store.
Why use it?
It makes useful working rules easier to review and apply instead of leaving them scattered across past session experience.

Command

1 yesterday A scan 0 tokens original MIT
View the source file jonase47/ccpr
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/jonase47/ccpr/instinct
Clone the repo
git clone --depth 1 https://github.com/jonase47/ccpr
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,171 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00000 $0.01171
Opus 5 $0.00000 $0.00585
Sonnet 5 $0.00000 $0.00234
Haiku 4.5 $0.00000 $0.00117

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

Security

Grade A, and why

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

commands/instinct.md · 89 lines

How it starts

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

Instinct Management

Manage instincts (confidence-based rules from session experience).

Actions

Determine the desired action from $ARGUMENTS:

list – Show all instincts

  1. Read ~/.claude/instincts.md (slim global Tier-1 index) — one-liner per entry already gives ID + confidence + theme
  2. Optional: load any of the topic files ~/.claude/instincts/{agents,files,workflow,shell-git,external}.md for full Rule/Why/How when the user wants details
  3. Search all docs/memory/*/instincts.md (agent instincts)
  4. Check whether docs/instincts.md exists (project instincts)
  5. Check whether docs/memory/MEMORY.md exists (project memory as cross-reference)
  6. Show all instincts grouped by scope (Global / Agent / Project) with ID and confidence
  7. If project memory exists: show number of memory entries as info

add [rule] – Create a new instinct

  1. Ask the user for the scope:
    • Global (G-NNN): Applies to all agents → add the H3 Rule block to the matching topic file under ~/.claude/instincts/{theme}.md, then add a one-liner bullet to ~/.claude/instincts.md (slim index). Pick the topic file by domain (agents / files / workflow / shell-git / external).
    • Agent (XX-NNN): Applies to one agent → docs/memory/{agent}/instincts.md
    • Project (P-NNN): Applies only in the current project → docs/instincts.md
  2. Generate the next available ID for the chosen scope
  3. Create the instinct with confidence 0.4:
### [ID] Short title
- **Confidence**: 0.4
- **Source**: User feedback from DD.MM.YYYY
- **Last confirmed**: DD.MM.YYYY
- **Rule**: [Rule from $ARGUMENTS]
- **Context**: [Ask the user for the context]
  1. Add it to the chosen file (global → topic file + index bullet; agent → that agent's instincts.md; project → docs/instincts.md)
  2. Update "Last updated"

confirm [ID] – Confirm an instinct

  1. Find the instinct with the given ID (global, agent, or project)
  2. Increase confidence by 0.1 (max 0.9)
  3. Update "Last confirmed" to today
  4. Show the updated instinct

Read the full file on GitHub · 89 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 · 89 lines · 0 tokens per session scan A ea0182ddac04

Subscribe to this mod's changes

instinct is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,171 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-31.

agentic-workflowsai-agentsanthropicclaudeclaude-codeclaude-code-agents
Related

Other commands, from other repositories

drift

Post-implementation spec drift check — verify the implementation matches existing OpenSpec specifications.

clay-good/OpenLore · 16 tokens

feature

Orchestrate a complete feature through discovery, spec, implementation, and review.

jcarlosrodicio/opencode-agent-orchestration-kit · 16 tokens

research

Research a technical or product question.

jcarlosrodicio/opencode-agent-orchestration-kit · 7 tokens

tidy

Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.

OdinMB/ops-workflow · 33 tokens

clean-check

Analyze code for cleanliness issues (unused code, comment quality, formatting, naming, complexity). Delegates to the code-cleanliness agent.

TeamManagementPlugin/claude-plugin · 27 tokens

build

Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.

ralfstrobel/agentic-brownfield-coding · 17 tokens