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-gemini-cli-extension --skill proceedgit clone --depth 1 https://github.com/OutlineDriven/odin-gemini-cli-extensionWrote 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-gemini-cli-extension/proceed)<a href="https://agentmods.dev/skills/outlinedriven/odin-gemini-cli-extension/proceed"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-gemini-cli-extension/proceed.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.1 | $0.00046 | $0.00400 |
| Opus 5 | $0.00023 | $0.00200 |
| Sonnet 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 8d 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.
This is a copy
100% identical to proceed — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 8d ago First seen · 46 lines · 46 tokens per session scan A 17178866a625
proceed is a skill published in the GitHub repository OutlineDriven/odin-gemini-cli-extension (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 400 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to proceed, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
github-triage
Triage GitHub issues through a configurable label-based state machine. Use when user wants to triage incoming issues, prepare issues for an autonomous agent, or move an issue between workflow states. Repo inferred from git remote; all GitHub calls go through gh.
to-issues
Decompose a plan, PRD, or spec into independently-grabbable vertical-slice issues (markdown file by default, GitHub issues via flag). Trigger when the user wants implementation tickets, work decomposition, or to convert an implementation plan into parallelizable work. Takes a plan file and emits atomic vertical slices.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
deliver
Drive a whole phase or feature-set to "merged + Done" — themed batching over /drive, front-loaded architectural questions, phase-gate ceremonies, and lossless resume. The long-horizon recipe ABOVE /drive; pair with native /goal " delivered" for hands-off, multi-turn completion.
drive
Drive one tracker ticket end-to-end — claim, plan, implement, verify, cross-review, and ship — autonomously, pausing only for architectural decisions. The per-ticket recipe; pair with native /goal " is merged" for unattended multi-turn completion.
autopilot
Take a product idea from the discovery interview all the way to a running delivery loop — drive the spec chain (BRIEF → PRD → SPEC → CONTEXT → phases.yaml → tracker), pausing ONLY at the human approval gates, then roll into /deliver. The single front door for a new forge product; pair with native /goal for hands-off…