feat(cli-tooling): add generic CLI, tooling and script-placement rules

Extracted from the per-agent profile files and the private ai-agents skill,
where they were duplicated and environment-coupled:

- discovery over guessing: walk the help tree, never invent flags, never
  hand-roll a script when a dedicated CLI exists
- non-interactive invocation: explicit targets, the tool's own --wait
- machine-readable output flags (json/compact/csv) vs. never filtering
  diagnostics
- orient before starting: project instructions, git log, prior work records,
  and verifying TODOs against the code
- script placement: dedicated version-controlled dir, symlinked into PATH
- destructive/outward-facing command care; environment drift verification

coding-dev.md and code-languages/bash.md now cross-reference it instead of
carrying their own one-line versions.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

code-languages/bash.md

@@ -161,12 +161,15 @@ mistakes before a human does.
 
 ## 9. Script Placement
 
-Standalone utility scripts belong in a **dedicated scripts directory**, symlinked into `PATH`
-rather than copied there. Never write a loose script directly into `~/.local/bin` or another
-`PATH` directory — the source of truth should be one versioned location.
+Standalone utility scripts belong in a **dedicated, version-controlled scripts directory**,
+symlinked into `PATH` rather than copied there. Never write a loose script directly into
+`~/.local/bin` or another `PATH` directory — the source of truth should be one versioned
+location. See [`../cli-tooling.md` §5](../cli-tooling.md) for the reasoning and the pattern.
 
 ---
 
 ## 10. Related
 - [`../coding-dev.md`](../coding-dev.md) — the general rules this extends.
+- [`../cli-tooling.md`](../cli-tooling.md) — invoking other tools *from* these scripts:
+  discovery, non-interactive flags, structured output.
 - [`python.md`](./python.md) — where a shell script should have become a Python script.