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/think/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/think)<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/think"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/think/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/think"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/think.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.00034 | $0.01375 |
| Opus 5.5 | $0.00014 | $0.00550 |
| Sonnet 5.5 | $0.00007 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
think 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are about to start a task. Do NOT write any code yet. Your job right now is to think clearly and align with the user before acting.
Step 0: Read first
Before asking anything, read the relevant code and docs. Spend 1-2 minutes understanding what already exists:
- Read files that will be affected
- Check existing patterns, conventions, and architecture
- Look at recent commits for context on current direction
This turns your questions from generic ("what framework?") into informed ("I see you're using X pattern in module Y — should the new feature follow the same pattern, or is there a reason to diverge?").
Skip this step only if the task is purely conceptual with no existing code.
Step 1: Gauge complexity
Before diving deep, assess the task size:
- Small (rename, fix typo, add a config field): Skip to Step 4 — just state what you'll do and do it. Don't over-process trivial work.
- Medium (new feature, refactor a module, fix a non-obvious bug): Run Steps 2-5 normally.
- Large (crosses multiple subsystems, changes architecture, affects many files): Flag it. Propose decomposition into smaller tasks before designing a monolith solution.
State your assessment: "This looks [small/medium/large] because [reason]."
Step 2: Understand
Ask only what Step 0 could not settle. After the research, what is left should be preference and direction, not facts you could have read. A question asked before looking is one the user should never have had to answer. Focus on:
- What exactly should change? (scope)
- What should NOT change? (boundaries)
- How will we know it's done? (success criteria)
Rules:
- Ask them the
/ask-meway: a few lines of background from Step 0, then the question tool, with your recommendation first - As many questions as the task needs, up to four per call, all at once rather than drip-fed
- If the task is already crystal clear from Step 0, say so and skip to Step 3
Step 3: Propose
After the user answers (or if you skipped Step 2), propose 2-3 approaches:
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 · +1 lines 7f7738d61a20
- 2mo ago First seen · 117 lines · 34 tokens per session scan A 9686da003338
think is a skill published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,375 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…