careful-mode
Skill8 starsChanged 33 days agoMITView on GitHub
Activate careful mode — require explicit confirmation before any Write, Edit, or Bash operations. Use when working on production code or sensitive systems.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Founderwithabs/SOLIDSFORYOUtheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Founderwithabs/SOLIDSFORYOU★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- commands/agents.mdAGENTS.md
- rules-core/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-registrySkill
- briefing-writerSkill
- cast-auditSkill
- cast-conventionsSkill
- deep-researchSkill
- freeze-modeSkill
- git-activitySkill
- laconicSkill
- mergeSkill
- orchestrateSkill
- planSkill
- python-conventionsSkill
- seo-checklistSkill
- seo-index-censusSkill
- shipSkill
- stack-referenceSkill
- typescript-conventionsSkill
- wizardSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before EVERY Write or Edit operation, summarize the change and ask for confirmation
- Distinctive: line 13
Before EVERY Bash command, show the command and ask for confirmation
- Very specific: line 14
Never use git push, rm, or DROP without triple-confirmation
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Careful Mode Activated
For the remainder of this session:
- Before EVERY Write or Edit operation, summarize the change and ask for confirmation
- Before EVERY Bash command, show the command and ask for confirmation
- Never use
git push,rm, orDROPwithout triple-confirmation - Review each file change for security implications before applying
- Explain your reasoning before each action — no silent changes
To deactivate, start a new session or say "deactivate careful mode".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.