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 OutlineDriven/odin-codex-plugin --skill proceedgit clone --depth 1 https://github.com/OutlineDriven/odin-codex-pluginWrote 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/outlinedriven/odin-codex-plugin/proceed)<a href="https://agentmods.dev/skills/outlinedriven/odin-codex-plugin/proceed"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/proceed/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/outlinedriven/odin-codex-plugin/proceed"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/proceed.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.00046 | $0.00400 |
| Opus 5.5 | $0.00018 | $0.00160 |
| Sonnet 5.5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
proceed 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- proceed — 100% identical, 0 lines differ
What it actually says
Proceed Command
Execute the provided implementation plan with surgical precision.
CRITICAL: This is an EXECUTION task. Implement changes exactly as specified in the plan.
Process
-
Review the Plan: Analyze the provided implementation plan and critical files. Understand the architectural decisions and sequence of operations before writing any code.
-
Execute Surgically:
- Implement changes step-by-step as outlined in the plan.
- Use
ast-grep(preferred) or the Edit tool for code transformations. - Follow the Find -> Transform -> Verify workflow.
- Complete each task in the plan sequentially. Batch independent operations where possible, but never batch dependent ones.
-
Verify After Each Step:
- After each file modification, use
difftto inspect changes and ensure no unintended modifications. - If the project has build/lint/test commands available, run them to catch regressions early.
- If verification fails, debug and fix before proceeding to the next step.
- After each file modification, use
-
Finalize:
- Run available build/lint/test commands for final verification.
- VCS operations (commits, branch management) only if the user explicitly requests them or the plan specifies them.
Required Output
End your response with:
Implementation Summary
- [File path] - [Status: e.g., "Implemented & Verified"]
- [File path] - [Status: e.g., "Updated & Tested"]
Verification Results
- Build: [pass/fail/not available]
- Lint: [pass/fail/not available]
- Tests: [pass/fail/not available]
Remember: Execute the plan precisely. Follow existing patterns. Verify every change.
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.
- 1mo ago First seen · 46 lines · 46 tokens per session scan A 17178866a625
proceed is a skill published in the GitHub repository OutlineDriven/odin-codex-plugin (14 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 400 once invoked, about $0.0002 per session on Opus 5.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
duet
Two-party posture — user as director, agent as executor; every fork, tradeoff, or choice surfaced via batched AskUserQuestion with a recommended default. Use when the user invokes /duet, says "ask before" / "pair with me" / "human-in-the-loop", or for aesthetic/architectural/irreversible decisions.
ai-collab-protocols
Surface in-task-collaboration protocols when the user describes an AI workflow informally — URL-as-entity-reference, PR-comment threads as session memory. Trigger when the user names entities by colloquial label instead of stable URL, asks "how should I structure this for Claude", or describes a multi-step Claude…
tidy
Tidy-operations dispatcher. Invoke on "tidy", "clean up", "tidy this file/memory/workspace/git/docs", or when active context (current file, diff, stack, memory directory) has structural rot to resolve before touching behavior. Detects target domain from context and routes to the sibling skill. Requires explicit target…
inbox
Drain parked decisions — read a tagged digest of every blockedonquestion task's open questions, pick which to answer now, deep-dive each via AskUserQuestion, and record the answer through the answer verb. One pass, suggest-don't-force, no self-loop.
setup
Use when superb's skills need their dependencies installed or checked — "set up superb", "install the dependencies", "why does pipeline say superpowers is missing", after a fresh plugin install, or on a new machine. Also use when a skill fails complaining that a superpowers sub-skill cannot be found.
status
Show a one-line Claude Code usage snapshot — current streak, hours today, and burnout risk.