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/usefulmove/enso/enso-referencenpx skills add usefulmove/enso --skill enso-referencegit clone --depth 1 https://github.com/usefulmove/ensoWhat 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.00043 | $0.01034 |
| Opus 5 | $0.00022 | $0.00517 |
| Sonnet 5 | $0.00009 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
enso-reference 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
Load this skill when:
- You need a quick reference for enso conventions or directory structure
- A user asks "what is enso?" or "how does this project work?"
- You are orienting yourself in an active enso project mid-session
- You want to see the current project status: active stories, log count, lessons
This is a read-only skill. No files are modified.
Reference
ENSO — Seam-Oriented Harness Protocol
A minimal system for managing AI agent context across sessions. Treats context as a scarce resource — load only what's needed, persist before it's lost, compact before overflow.
Key Skills
| Skill | Purpose |
|---|---|
session-start |
Start session. Loads PRD, ARCHITECTURE, LESSONS, recent logs, and detects the active story. Bootstraps new projects on first use. |
session-persist |
Close/pause session. Drafts a session log, lessons, and story updates for your review. Writes nothing until confirmed. |
read-session-logs |
Show last N session logs (default: 5). Read-only. |
enso-reference |
Show this reference. |
The Six Operations
| Operation | What It Does |
|---|---|
| Write | Persist information outside the context window |
| Select | Load only what's needed right now |
| Probe | Actively search (grep, LSP, glob) for answers |
| Compress | Summarize to fit the token budget |
| Isolate | Split work across scopes |
| Assign | Match task to the right agent |
Directory Structure
docs/
core/ # Source of truth
PRD.md # Problem, goals, scope
ARCHITECTURE.md # System overview, key decisions
QUEUE.md # Optional: prioritized story scheduler
stories/ # Active work items (one file per story)
reference/ # Long-term memory
LESSONS.md # Accumulated patterns and gotchas
completed/ # Finished stories
skills/ # Reusable procedures and scripts
logs/ # Session history (auto-generated by session-persist)
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 · 122 lines · 43 tokens per session scan A 983581cc495e
enso-reference is a skill published in the GitHub repository usefulmove/enso (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,034 once invoked, about $0.0002 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-31.
Other skills, from other repositories
harness
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때, (5) '하네스 점검', '하네스 감사', '하네스 현황', '에이전트/스킬 동기화' 등 기존 하네스 운영/유지보수 요청 시 사용.
new-plugin
Factory line for adding a new HAR verification plugin (like playwright or rocketsim) for any framework — research the framework docs, build the template under src/templates/plugins/, register it everywhere, validate on a real repository, and open a PR. Use when asked to add/create a plugin, plugin template, or…
v1-milestone
Factory line for executing one milestone of the HAR v1.0.0 refactor (epic os-factory/har#225) — plan the wave of parallel subagents, implement each issue in its own HAR slot, ship stacked PRs, run the fixture-e2e milestone gate, and hand off for review. Use when asked to "run the next v1 milestone", "work on v1.0.0"…
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
diff-driven-docs
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.
plan-review-gate
Use after saving a non-trivial plan or decision RFC when a fail-closed feasibility, completeness, and alignment review must block execution.