onebase: Skill for Claude Code

.agents/skills/plan-approved/SKILL.md

plan-approved is a skill for Claude Code, Codex from ivanarama/onebase. It costs 50 tokens per session (348 once invoked), scanned A, original, MIT.

A workflow for creating a technical planning pull request for approved onebase issues marked for planning. It defines eligibility checks, required project files, isolated worktrees, and what the workflow must not do.

In plain words
What is it for?
Use it to create a plan-only pull request for an eligible issue, following the repository’s plan format and commit requirements.
Why use it?
It keeps planning separate from implementation and prevents an approved issue from being changed, merged, or shipped prematurely.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; installed under .agents/ (shared by several agents).

This is ivanarama/onebase's own configuration. It tells Claude Code and Codex how to work on onebase itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything onebase configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ivanarama/onebase. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ivanarama/onebase/main/.agents/skills/plan-approved/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ivanarama/onebase

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for plan-approved

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivanarama/onebase/plan-approved.svg)](https://agentmods.dev/skills/ivanarama/onebase/plan-approved)
Your own site
<a href="https://agentmods.dev/skills/ivanarama/onebase/plan-approved"><img src="https://agentmods.dev/badge/skills/ivanarama/onebase/plan-approved.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 348 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00348
Opus 5 $0.00025 $0.00174
Sonnet 5 $0.00010 $0.00070
Haiku 4.5 $0.00005 $0.00035

Measured 2d ago against content hash 7d64b0476ef9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

plan-approved 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 2d 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.

.agents/skills/plan-approved/SKILL.md · 17 lines

What it actually says

Codex-адаптер этапа PLAN

  1. До действий полностью прочитать каноническую процедуру .claude/skills/plan-approved/SKILL.md.
  2. Сначала применять AGENTS.md, затем совместимые соглашения CLAUDE.md и Plans/README.md.
  3. $plan-approved [N] — эквивалент /plan-approved <N>. Номер не обходит eligibility-гейт.
  4. Перед GitHub-мутациями проверить gh и логин ivanarama; непосредственно перед записью перечитать issue/PR.
  5. Создавать только plan-PR в изолированном worktree. Не писать продуктовый код, не ставить ship, не сливать PR и не запускать FIX.
  6. На Windows сохранять UTF-8-процедуру, Get-Content -Encoding UTF8 -Raw, проверку через @base64 и сравнение байт-в-байт.
  7. В коммите использовать Generated-with: Codex. Сохранять приоритеты, маркеры, переходы меток и точный формат ИТОГ: канонической процедуры.

Логика конвейера живёт в канонической процедуре; этот файл — только адаптер Codex.

Changes

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.

  1. 2d ago First seen · 17 lines · 50 tokens per session scan A 7d64b0476ef9

Subscribe to this mod's changes

plan-approved is a skill published in the GitHub repository ivanarama/onebase (90 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 348 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories

streamsql

当需要创建实时数据聚合/窗口统计、流式过滤转换、变化检测(CDC)、生命周期累计、元数据富化(流-表 JOIN)、CEP 模式识别(MATCHRECOGNIZE)等规则链时使用,或当使用 x/streamAggregator 和 x/streamTransform 组件时使用。包含 SQL 语法、窗口、分析函数、JOIN、CEP 和配置示例.

rulego/rulego · 90 tokens

editing-model-diagrams

Creates, edits, reviews, and regenerates C4 architecture diagrams written with goa.design/model and the mdl CLI. Use when changing Model DSL, model.go or views.go files, system landscape, context, container, component, dynamic, or deployment views, element relationships, boundaries, layout, or generated SVG diagrams.

goadesign/model · 69 tokens

writing-git-commits

Write clear, focused Git commit messages and keep commits easy to review.

patriceckhart/zot · 14 tokens

conventional-git

Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…

Harmeet10000/skills · 77 tokens

octocat

Handles git and GitHub operations using the gh CLI. Use when the user asks about pull requests (PRs), GitHub issues, repo management, branching, merging, rebasing, cherry-picking, merge conflict resolution, commit history cleanup, pre-commit hook debugging, GitHub Actions workflows, or releases. Covers creating and…

Harmeet10000/skills · 100 tokens

1c-db-load-git

Загрузка изменений из Git в базу 1С. Используй когда пользователь просит загрузить изменения из гита, обновить базу из репозитория, partial load из коммита.

Desko77/cursor-1c-skills · 47 tokens