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/self-check/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/self-check)<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/self-check"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/self-check/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/self-check"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/self-check.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.00024 | $0.02452 |
| Opus 5.5 | $0.00010 | $0.00981 |
| Sonnet 5.5 | $0.00005 | $0.00490 |
| Haiku 4.5 | $0.00002 | $0.00245 |
Grade B, and why
self-check scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `grep -n 'jq -r' templates/.claude/hooks/*.sh` — every hit must sit inside a `command -v jq` branch that has an `else`. Five jq-only reads shipped broken before this was checked; git-guard's made the whole guard dead c How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pause and honestly answer every question below.
1. Am I still on track?
- What is the user's current goal? (The user may have pivoted — their latest direction IS the goal.)
- What am I doing right now?
- Is my current action directly serving the user's current direction, or have I drifted?
- If I drifted: stop and re-align.
- If the user changed direction: follow immediately. The user decides priorities.
2. Am I progressing or circling?
- Have I edited the same file more than twice?
- Did I fix something, then break something else, and now I'm fixing that?
- Am I adding workarounds (try/catch, if/else guards) instead of addressing root cause?
- Am I trying things without understanding why they might work?
- If yes to any: pause. List all attempted fixes, look for the common root cause, report to user.
3. Am I being rigorous?
- Are all my "verified" or "working" claims backed by actual execution output?
- Have I marked anything ✅ without pasting the verification command and output?
- Have I marked something "done" when it depends on an external resource I haven't tested against?
- Have I ruled out my own assumptions before attributing failure to an external tool/library?
- Am I quoting tool output verbatim, or have I altered/paraphrased it?
- Is there anything I stated confidently but am actually unsure about?
- Am I suggesting to compact or start a new session? This impulse is understandable in long sessions, but you can't see context percentage and the system handles compacting automatically. If the urge comes from task difficulty rather than a real technical limit, re-read progress.md and continue.
- If any claims need correcting: do it now. Label uncertain claims as "unverified" or "assumption". Downgrade unverified ✅ to ⚠️ with reason.
4. Am I respecting scope?
- Am I making changes the user didn't ask for? (refactoring, "improving", adding features)
- Am I about to do something irreversible without asking?
- Am I following the debugging process (gather → hypothesize → verify → fix)?
- If scope has crept: re-focus on what was asked.
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 · +10 lines 73e215073776
- 2mo ago First seen · 127 lines · 24 tokens per session scan B 8f7e33d1d335
self-check is a skill published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 2,452 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…