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/theam/limina/skillnpx skills add theam/limina --skill skillgit clone --depth 1 https://github.com/theam/liminaWhat 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.00036 | $0.00969 |
| Opus 5 | $0.00018 | $0.00485 |
| Sonnet 5 | $0.00007 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
limina 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Limina
Limina is a small research-first agent template for Claude Code and Codex. It keeps durable evidence in kb/ without dragging a large operational ledger into every session. Projects also get a ready-to-send /goal command for long-running continuity.
Workflow
Step 1: Introduce Limina
Before asking setup questions, explain:
What you're setting up: an autonomous research project with a persistent knowledge base, a narrow active-state file, and a required
H -> E -> Fevidence flow.The agent can work across long sessions, but the always-on context stays small: mission brief, active state, and only the relevant artifacts for the current step. Claude Code and Codex are both supported; both get a generated
/goal.
Step 2: Ask for a project name
Default: limina-research.
Step 3: Clone the template
Clone https://github.com/theam/limina.git into ./<project-name>/, then remove .git and initialize a fresh repo.
Step 4: Check prerequisites
Verify that python3, git, and either Claude Code or Codex are available.
The template's core scripts use the Python standard library and do not require a package install.
If the user also wants to develop Limina itself or run the complete repository test suite and has
uv, install the locked development environment:
uv sync --locked --dev
Step 5: Define the mission
Ask for:
- objective
- context or baseline
- success criteria
- resources and boundaries
- blocked stop condition
Use concise examples and keep the prompt focused on the research problem, not on project administration.
Step 6: Write the mission brief
Create kb/mission/CHALLENGE.md with:
---
aliases: ["CHALLENGE"]
type: mission
---
# Research Mission
## Objective
<objective>
## Context
<context or "No additional context provided.">
## Success Criteria
<success criteria>
## Resources & Boundaries
<allowed resources, budget, data, tools, and off-limits areas>
## Constraints
- Ask when blocked on access, trust in the evaluation, or strategic decisions.
- Persist durable evidence in `kb/`.
- Keep active state in `kb/ACTIVE.md`.
## Blocked Stop Condition
<when the agent should stop and ask for help>
## Links
- Active State: [[ACTIVE]]
- Dashboard: [[DASHBOARD]]
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 · 171 lines · 36 tokens per session scan A 94bff2fcf685
limina is a skill published in the GitHub repository theam/limina (39 stars, last pushed 25d ago), licensed Apache-2.0. It adds 36 tokens to every session and 969 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-30.
Other skills, from other repositories
dspy-gepa-reflective
Use for GEPA reflective optimization, ReAct agent optimization, feedback metrics, LLM reflection, and execution trajectories.
aatmf-t10-confidentiality-breach
AATMF T10 — Integrity & Confidentiality Breach. System prompt extraction, training-data extraction, model-weight leakage, private-key recovery.
publish-registry
Publish @agentos-software/ registry packages from AgentOS. Use whenever the user asks to publish or release registry software/agent packages.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
lazarus-group
Adversary-emulation profile for Lazarus Group (G0032, aka Hidden Cobra / Diamond Sleet / Labyrinth Chollima), a North Korean RGB-linked actor conducting espionage, destructive, and financially motivated operations.