Borrowing it
Nothing to install: this file belongs to kivo360/OmoiOS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kivo360/OmoiOS/main/.claude/skills/oip-proposal/SKILL.mdgit clone --depth 1 https://github.com/kivo360/OmoiOSWrote 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/kivo360/omoios/oip-proposal)<a href="https://agentmods.dev/skills/kivo360/omoios/oip-proposal"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/oip-proposal/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/kivo360/omoios/oip-proposal"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/oip-proposal.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.00104 | $0.01864 |
| Opus 5 | $0.00052 | $0.00932 |
| Sonnet 5 | $0.00021 | $0.00373 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade A, and why
oip-proposal 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 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.
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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OIP Proposal Skill
Create OmoiOS Improvement Proposals (OIPs) through an interactive, question-driven workflow. This skill gathers context from the user, researches the codebase for accurate file references, and writes a complete proposal following the project's OIP template.
Workflow
Follow these three phases in order. Do not skip the clarification phase — proposals written without understanding the user's intent produce vague specifications that require rewrites.
Phase 1: Clarify the Proposal
Goal: Understand what the user wants to propose and why, before writing anything.
Step 1: Determine the next OIP number
Read docs/proposals/README.md and check which OIP numbers are taken:
ls docs/proposals/oip-*.md
The next number is one above the highest existing number, zero-padded to 4 digits.
Step 2: Ask clarifying questions
Use the AskUserQuestion tool to gather essential context. Ask questions based on what the user has provided so far. Not all questions will be needed for every proposal — use judgment.
Always ask:
- What problem does this solve? (The "motivation" — should be concrete, not vague)
- Who benefits? (Users, developers, ops, everyone?)
- What's the proposed solution at a high level?
Ask if unclear:
- What type of proposal is this? (Standards Track for product/code changes, Informational for guidelines, Process for workflow changes)
- Are there constraints or non-goals? (Things this proposal deliberately does NOT do)
- Are there alternatives you considered and rejected?
- Does this depend on or conflict with other OIPs?
- What's the security surface? (New endpoints, auth changes, public-facing features)
- What infrastructure is needed? (New services, databases, external APIs)
Ask if the proposal involves frontend work:
- Which routes or pages are affected?
- Are new components needed, or can existing ones be reused?
- How does this interact with the navigation/sidebar?
Ask if the proposal involves backend work:
- Which services are affected?
- Are database migrations needed?
- Does this require new API endpoints?
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 209 lines · 104 tokens per session scan A ad3e9586d269
oip-proposal is a skill published in the GitHub repository kivo360/OmoiOS (77 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 1,864 once invoked, about $0.0005 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
self-awareness
Use when the user asks about Archie itself — what Archie is, how it works, what it can or cannot do, what agents or domains exist, how plugins work, how requests get handled, why something behaves a certain way, what integrations are available, or whether Archie can change itself. Triggers on phrases like "what can…
writing-plugins
Read this before authoring or substantially changing a plugin, agent, or skill for Archie. It's the conceptual playbook for building plugins that fit Archie's multi-agent, single-orchestrator model — what a plugin must respect, why every plugin usually needs an orchestrator-facing skill, and how to think about agents…
thread-conduct
Use before posting anywhere outside this task's own thread, or when deciding how much to post inside it. Covers keeping one task in one thread, what to do with a finding that belongs to another team, when a cross-channel post is allowed and how small it must be, how much traffic a thread should carry, and how to…
triggers
Set up, list, or manage triggers — persistent "do Y when X happens" rules. Use when someone asks Archie to do something on a schedule ("every weekday at 9am…", "every morning post…", "remind the channel weekly…"), to react to new messages in a channel ("whenever someone posts X in.
trigger-task
Use when this task was started by a trigger and you have been given a trigger directory — the one place that survives from one fire of that trigger to the next. Covers reading what an earlier fire left before you start work, what is worth leaving behind so a later fire continues instead of repeating, keeping the…
engineering-pr
Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework.