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 skills add DanialDaeHyunNam/omniscitus --skill migrategit clone --depth 1 https://github.com/DanialDaeHyunNam/omniscitusWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/danialdaehyunnam/omniscitus/migrate)<a href="https://agentmods.dev/skills/danialdaehyunnam/omniscitus/migrate"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/migrate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/danialdaehyunnam/omniscitus/migrate"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00064 | $0.09430 |
| Opus 5 | $0.00032 | $0.04715 |
| Sonnet 5 | $0.00013 | $0.01886 |
| Haiku 4.5 | $0.00006 | $0.00943 |
Grade D, and why
omniscitus-migrate scanned grade D with 2 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 9d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`~/.claude/settings.json` → `statusLine.command` points at). Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .omniscitus How it starts
The opening of the file, as written. The whole thing — 948 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Omniscitus Migrate — Bring Any Existing Project Into Omniscitus
Analyze an existing codebase and bootstrap the full .omniscitus/ structure
from what already exists: docs, git history, test code, and conversation
with the user.
When to Use
- User types
/omniscitus-migrate - Applying omniscitus to a project that already has code, docs, and tests
Instructions
Pre-check A: Git Repo Required (uninstall safety)
Omniscitus writes to a few files outside .omniscitus/ (e.g., CLAUDE.md,
member docs). The ability to cleanly uninstall later depends on a git
repo — we record a pre-migration anchor commit SHA so those files can be
reverted surgically. Without git, rollback is entirely manual.
git rev-parse --show-toplevel 2>/dev/null
If this fails (non-zero exit / empty output):
Use AskUserQuestion:
-
question: "Omniscitus's clean uninstall depends on a git repo. How to proceed?"
-
options:
- "
git initfirst (Recommended)" - "Proceed without rollback safety"
- "Abort"
- "
-
"init first" → run
git init && git add -A && git commit -m "baseline: pre-omniscitus"then continue. -
"proceed without" → continue but flag
git_project: falseinanchor.yaml. Uninstall will be entirely manual. -
"abort" → stop here.
If git repo is present but dirty (git status --porcelain non-empty):
Warn: "You have uncommitted changes. The anchor SHA will record the last committed HEAD, so uncommitted edits will NOT be covered by rollback. Commit or stash first for the safest migration."
Use AskUserQuestion:
- options: "Commit first" / "Continue anyway"
Pre-check B: Record the Anchor
Before any file is written (outside .omniscitus/ or inside), create
.omniscitus/migrate/anchor.yaml:
version: 1
# Pre-migration git state — the point /omniscitus-uninstall reverts to.
anchor:
sha: {git rev-parse HEAD}
branch: {git branch --show-current or "HEAD detached"}
timestamp: {now ISO 8601}
git_project: true # false if user chose "Proceed without"
# Plugin version that last wrote the canonical footprint content
# (CLAUDE.md block, statusline block, README, …). Bumped by /migrate and
# /omniscitus-update. SessionStart's version-check compares this against
# the installed plugin version to nag the user about staleness.
migrate_version: {plugins/omniscitus/.claude-plugin/plugin.json → version}
# Files modified OUTSIDE .omniscitus/ by any omniscitus skill.
# Every external write must append an entry here so uninstall can
# surgically reverse them. Paths are relative to the project root.
footprint: []
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.
- 9d ago First seen · 948 lines · 64 tokens per session scan D 6f2b0a32cc56
omniscitus-migrate is a skill published in the GitHub repository DanialDaeHyunNam/omniscitus (5 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 9,430 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.