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/q00/ouroboros/updatenpx skills add Q00/ouroboros --skill updategit clone --depth 1 https://github.com/Q00/ouroborosWrote 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/q00/ouroboros/update)<a href="https://agentmods.dev/skills/q00/ouroboros/update"><img src="https://agentmods.dev/badge/skills/q00/ouroboros/update.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00996 |
| Opus 5 | $0.00007 | $0.00498 |
| Sonnet 5 | $0.00003 | $0.00199 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ouroboros:update
Check for updates and upgrade Ouroboros without changing the installation's manager, environment, or optional-dependency profile.
Usage
ooo update
/ouroboros:update
Trigger keywords: "ooo update", "update ouroboros", "upgrade ouroboros"
Instructions
When the user invokes this skill:
-
Use the native command as the single source of truth:
ouroboros update --check-
If it reports up to date, report that result and stop.
-
If it reports an update available, ask the user to choose Update now or Skip.
-
If the user chooses Update now, run:
ouroboros update --yesWhen the user actively uses both Claude Code and Codex, refresh both host integrations without changing the configured execution backend:
ouroboros update --yes --runtime all
Show the command's result. The native updater binds the package upgrade and post-update setup to one receipt-backed installation identity: manager, environment, recorded profile, and environment-local console script.
-
-
If the check exits unsuccessfully but
ouroboros update --helpworks, report the native error and stop. Do not replace it with a manual updater. In particular, do not infer ownership from globaluv tool list,pipx list, PATH order, directory names, or the active agent runtime. -
If
ouroboros update --helpdoes not work, this is a legacy installation that predates the receipt-bound updater. Fail closed:- A read-only
ouroboros --versioncheck is allowed. - Explain that the old skill cannot prove the original manager, environment, and extras/profile, so it will not mutate the installation.
- Ask the user to rerun the exact original install command (including its
ouroboros-ai[...]extras and custom manager root) to reach a version with the native updater. - If the user does not know that identity, recommend a fresh isolated install rather than guessing.
- Do not run package upgrades, plugin refreshes, or setup commands from this legacy path.
- A read-only
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.
- 4d ago First seen · 111 lines · 14 tokens per session scan A 353d36929ecb
update is a skill published in the GitHub repository Q00/ouroboros (5,747 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 996 once invoked, about $0.0001 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
llm-pipeline
Use when wiring several LLM calls into a production flow: typed contracts between steps, a router/gateway so 429s, timeouts and outages fail over instead of taking you down, and cost control via caching, model tiers and abort caps. NOT single-prompt wording (that is prompt-engineering), NOT a model-driven tool loop…
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.