Borrowing it
Nothing to install: this file belongs to TechHU-GS/cc-discipline. 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/TechHU-GS/cc-discipline/main/.claude/skills/coplan/SKILL.mdgit clone --depth 1 https://github.com/TechHU-GS/cc-disciplineWrote 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/techhu-gs/cc-discipline/coplan)<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/coplan"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/coplan/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/techhu-gs/cc-discipline/coplan"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/coplan.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.00035 | $0.01759 |
| Opus 5.5 | $0.00014 | $0.00704 |
| Sonnet 5.5 | $0.00007 | $0.00352 |
| Haiku 4.5 | $0.00003 | $0.00176 |
Grade A, and why
coplan 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write the plan under discussion to docs/current-plan.md, then stop.
This skill does not produce the plan and does not decide anything. It takes whatever is on the table — the approaches from /think, or a plan just described in conversation — and puts it where a reviewer can read it. Codex runs read-only from the repo root, so a plan on disk is one it can check against the actual code. That is the entire point: a plan pasted into a prompt can only be judged on its own terms, while a plan in the tree can be judged against what is really there.
If there is no plan on the table yet — no approaches from /think, nothing described in conversation — say so and stop. Point at /think instead. Do not invent a plan just to have something to write: a fabricated plan sent for review wastes a review run and produces confident feedback on something nobody proposed. Fabricating content when a skill is invoked is the hardest failure mode to catch in yourself, which makes this the most important line in this file.
The file is a scratch file, not a record
It must not be tracked by git. Before writing, make sure docs/current-plan.md is in .gitignore; add the line if it is missing. If the file is already tracked, say so and offer to untrack it with git rm --cached docs/current-plan.md — do not run that silently, and never commit this file yourself.
- A tracked file that is always modified becomes a standing passenger. It sits in every
git status, so it rides into unrelated commits whenever anything sweeps the working tree. This has already happened: a commit whose message said it touched only documentation also carried temporary debug instrumentation ontomain. Untracking removes the passenger; telling someone to be careful does not —/commitalready says to stage selectively, and it happened anyway. - It is not where the decision lives. What was decided and why belongs in
docs/progress.mdand in commit messages. Do not create an archive directory for old plans: a third place holding the same facts only guarantees two of them go stale.
Known cost, accepted deliberately: because the file is untracked, hand-edits between revisions no longer show up in git diff, so you lose the view of what you just changed. Self-contradictions have survived several revisions unnoticed for exactly this reason. That cost is smaller than instrumentation reaching main. If a revision matters enough to remember, write the one sentence into progress.md — if you cannot write that sentence, it did not matter.
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 Changed · +2 lines cff387e30881
- 1mo ago Changed · +30 lines · +5 tokens per session 334b6df4f172
- 2mo ago First seen · 46 lines · 30 tokens per session scan A 77946c2d14a7
coplan is a skill published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,759 once invoked, about $0.0001 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-31.
Other skills, from other repositories
document-code
Decide whether a comment belongs, and write the ones that do — in Ruby, YAML, a Dockerfile, a shell script, tests or config. Use it before adding any comment, docstring or YARD block, including one you are about to write mid-implementation, and before deleting or rewording one already there. Use it when finished code…
create_plan
Create detailed implementation plans through interactive research and iteration.
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…