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 ytunahankskn/oh-meine-excode --skill consensus-planninggit clone --depth 1 https://github.com/ytunahankskn/oh-meine-excodeWrote 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/ytunahankskn/oh-meine-excode/consensus-planning)<a href="https://agentmods.dev/skills/ytunahankskn/oh-meine-excode/consensus-planning"><img src="https://agentmods.dev/badge/skills/ytunahankskn/oh-meine-excode/consensus-planning.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.00030 | $0.00306 |
| Opus 5 | $0.00015 | $0.00153 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
consensus-planning 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 7d 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.
What it actually says
Consensus Planning
Use this skill when the user wants to plan first or when the task is large enough that coding immediately would be wasteful.
This skill recreates the useful part of planner/architect/critic loops with Codex-native agents.
Planning Sequence
Run these steps in order:
- Local problem framing
- Optional
explorerpass for codebase facts defaultplanner passdefaultcritic or architect-style pass- Local synthesis into one actionable plan
Do not run planner and critic blindly in parallel when the critic depends on the planner's output.
Plan Requirements
Every plan should include:
- requirements summary
- acceptance criteria
- implementation steps
- risks and mitigations
- verification plan
For higher-risk work, also include:
- alternatives considered
- why the chosen direction wins
- likely failure modes
When To Ask The User
Ask only when the answer is a real product or business decision that cannot be inferred safely.
Do not ask the user for:
- codebase facts
- framework details you can inspect
- file locations you can discover yourself
Handoff Rule
If planning is followed by implementation, carry forward:
- chosen approach
- rejected alternatives
- known risks
- verification expectations
Keep the handoff compact and actionable.
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.
- 7d ago First seen · 60 lines · 30 tokens per session scan A ba06f4c416dd
consensus-planning is a skill published in the GitHub repository ytunahankskn/oh-meine-excode (2 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 306 once invoked, about $0.0002 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
windows-appshot
Use when the user invokes $windows-appshot or asks to create a Windows appshot bundle, including foreground-window screenshots, UI Automation text, metadata.json, prompt.md, or appshots generated by scripts/New-Appshot.ps1.
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration in proposals and decision-facing writing. Use when the user asks to rewrite or audit a proposal, plan, research contribution, executive summary, or similar text for directness. Do not use for ordinary code work or unrelated prose.
compact-kb
Use only when user explicitly invokes $compact-kb.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.