Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add DanialDaeHyunNam/omniscitus/plugin install 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/omniscitus-update)<a href="https://agentmods.dev/skills/danialdaehyunnam/omniscitus/omniscitus-update"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/omniscitus-update/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/omniscitus-update"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/omniscitus-update.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.00080 | $0.01467 |
| Opus 5 | $0.00040 | $0.00733 |
| Sonnet 5 | $0.00016 | $0.00293 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
omniscitus-update 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 11d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Omniscitus Update — Apply Latest Canonical Blocks
The plugin itself updates via /plugin install ..., but the content it
wrote into the project (the CLAUDE.md onboarding block, the statusline
indicator, .omniscitus/README.md) stays frozen at whatever version
/omniscitus-migrate last ran. This skill brings those in sync with the
currently installed plugin version — no full re-migration, no data loss.
Flow per footprint entry: detect current content → diff against the
new canonical → show the user → apply on consent → bump
anchor.migrate_version.
When to Use
- User types
/omniscitus-updateor says "plugin update apply" - SessionStart nag fired: "installed plugin is vX.Y.Z but anchor records vA.B.C — run /omniscitus-update"
Hard Rules
- Never touch files not listed in
.omniscitus/migrate/anchor.yaml'sfootprint. Scope is only what migrate previously wrote outside.omniscitus/. - Never overwrite a user-edited block silently. Show the diff, ask, apply only on explicit consent.
- Never re-run blueprint/history generation. That's out of scope —
use
/blueprint-syncor/wrap-upfor content, not canonical blocks. - Idempotent: running twice with nothing stale is a no-op that
still updates
anchor.migrate_versionso the nag silences.
Instructions
Step 1: Preconditions
Verify the project looks migrated:
.omniscitus/migrate/anchor.yamlexists → read it..omniscitus/history/_index.yamlexists (proof migrate actually ran).
If either is missing, tell the user:
📭 This project isn't migrated yet. Run /omniscitus-migrate first.
Stop.
Step 2: Discover Versions
Read:
- Installed plugin version:
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json→version - Recorded version:
anchor.migrate_version(may be absent on pre-0.6 anchors — treat as "unknown")
If they already match and every footprint entry's canonical content matches disk (see Step 3), report:
✅ Already up to date at v{installed}. Nothing to apply.
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.
- 11d ago First seen · 173 lines · 80 tokens per session scan A 3fd9fd158fe8
omniscitus-update is a skill published in the GitHub repository DanialDaeHyunNam/omniscitus (5 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,467 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…