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/omnigent-ai/omnigent/detect-frameworknpx skills add omnigent-ai/omnigent --skill detect-frameworkgit clone --depth 1 https://github.com/omnigent-ai/omnigentWhat 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.00031 | $0.00575 |
| Opus 5 | $0.00015 | $0.00287 |
| Sonnet 5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
detect-framework 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 3d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Detection
When the user has existing Python code they want to integrate into Omnigent, detect the framework from import statements and recommend the appropriate executor type.
Detection Procedure
-
Ask the user for the path to their agent code (or look for Python files in the current directory if filesystem access is enabled).
-
Scan Python files for import patterns. Check in this priority order:
| Import pattern | Framework | Executor type |
|---|---|---|
import anthropic or from anthropic + agent patterns (e.g. Agent, tool, system prompt setup) |
Claude SDK | claude_sdk |
import openai or from openai + agents patterns (e.g. Agent, Runner, function_tool) |
OpenAI Agents SDK | agents_sdk |
from langgraph or import langgraph |
LangGraph | Not natively supported yet |
from deepagents or import deepagents |
DeepAgents | Not natively supported yet |
from langchain or import langchain |
LangChain | Not natively supported yet |
from crewai or import crewai |
CrewAI | Not natively supported yet |
from autogen or import autogen |
AutoGen | Not natively supported yet |
| None of the above | Unknown | Not natively supported yet |
- Report what you found and recommend the executor type.
What to generate for each executor type
llm (default — no existing code)
Generate a standard agent directory:
executor:
type: llm # or omit entirely (llm is the default)
claude_sdk
The user's Claude SDK code runs directly. Generate config that points to their entry module:
executor:
type: claude_sdk
agents_sdk
The user's OpenAI Agents SDK code runs directly:
executor:
type: agents_sdk
Asking about unsupported frameworks
If the user's framework is not natively supported, let them know:
- Explain that Omnigent does not currently have a supported executor for that framework.
- Offer to show them a pre-filled GitHub issue URL requesting first-class support for their framework.
- If they want to start fresh instead, recommend generating a standard
llmagent. - The issue URL format:
https://github.com/dbczumar/omnigent/issues/new?title=...&body=...
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.
- 3d ago First seen · 67 lines · 31 tokens per session scan A 97d078eeed0d
detect-framework is a skill published in the GitHub repository omnigent-ai/omnigent (9,591 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 575 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
no-mistakes
Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach upstream. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.
mnemosyne-context
Load this when working on the mnemosyne memory system — its repo, sync server, memory databases, or CI. Covers architecture, the surface/sync data model, dev workflow (tests/ruff/CI matrix), release policy, and known gotchas that are easy to get wrong. Use for any "mnemosyne" dev or devops task, or when a…
hermes-memory-providers
Install and configure Mnemosyne as a Hermes Agent memory provider — local SQLite with vector search, episodic consolidation, and temporal knowledge graphs.
mnemosyne
Persistent cross-session memory via Mnemosyne — store, recall, and consolidate facts, preferences, and context.
autocontext
Iterative strategy generation and evaluation system. Use when the user wants to evaluate agent output quality, run improvement loops, queue tasks for background evaluation, check run status, inspect runtime artifacts and session branch lineage, or discover available scenarios. Provides LLM-based judging with…
autocontext-consumer
Use when an agent needs to USE knowledge Autocontext already produced - find which scenarios have knowledge, read the playbook and lessons for one, understand the on-disk file and folder layout, and move knowledge between checkouts. Host-agnostic; requires only the autoctx CLI and the filesystem.