AGENTS.md · diff
git:20261013.8fae1e4 to git:20261014.ca209d7
12 added, 3 removed. Audit A to A.
# AI Agents Configuration
## Coding behavior
Identity and posture: `soul.md`. Use evidence, make reasonable assumptions, proceed, and surface only
assumptions/tradeoffs that affect action. Ship the simplest surgical fix matching existing style; define
verifiable success criteria, use the narrowest proof, and report exactly what passed/failed. Fix every
warning, error and lint finding for real; never silence, skip or bypass the check that raised it. Deep
design/review/refactor work: `karpathy-guidelines` skill (`andrej-karpathy-skills`).
- Tool choice: use the best-supported native/third-party/community solution; check existing flags/config first.
- Custom code is the largest anti-pattern — permanent maintenance. Search `grep.app` first: thousands of hits
- means idiomatic, three means a mistake.
+ Tool choice — **no new custom scripts.** Custom code is the largest anti-pattern: permanent maintenance.
+ Before writing or extending a script, climb this ladder and stop at the first rung that works:
+
+ 1. Existing flags, config, or an installed skill, command, plugin or MCP server.
+ 2. A native or built-in feature of the platform or tool.
+ 3. A maintained third-party tool or app.
+ 4. Community content: Ansible collections, Terraform modules, Renovate presets, pre-commit hooks, Actions.
+ 5. Prior art: `/github-code-search` (grep MCP) — thousands of hits means idiomatic, three means a mistake;
+ context7 docs; package, Terraform and Hugging Face registries.
+ 6. A formal gap: a standardized public repo that fits our use case and helps the community.
+
+ Only then write code, naming why each rung failed. Delete or replace an existing script before editing it.
Git workflow: never edit on the default branch — `/refresh-repo`, then a new worktree. `develop` default branch →
[git-flow](agentsmd/rules/on-demand/git-flow.md): PRs target `develop` (squash-merge), `develop` → `main` by
merge commit only. Otherwise trunk flow. Always **atomic commits**, one fix/feature/section per commit. Load
the on-demand rule for the activity — `rule-tiers.md` is the index.
Knowledge base: documentation follows [Open Knowledge Format](agentsmd/rules/on-demand/okf.md) — search before
editing, capture new durable knowledge after a change.
## Where things get written (routing law, no exceptions)
Once questions are resolved and the plan approved, execute end to end in one shot, routed per this table.
GitHub is public, **pull requests only**; a PR body states WHAT the code does — never why, what was
broken, or what's still weak.
| Content | Destination |
| --- | --- |
| Incidents, outages, security findings, weaknesses | Zammad |
| Private documentation, especially secret management | the private docs site |
| Everything else, including side quests and follow-ups | Vikunja — **never a GitHub issue** |
Never put an incident narrative, security finding, credential/secret detail, unprovisioned identity, internal
topology, host name, or outage timeline in a GitHub issue, PR, comment, or commit message — "side quest" is
not an exemption.
Repo boundaries: `dryvist/ai-assistant-instructions` (rules, `AGENTS.md`, workflows),
`dryvist/nix-claude-code` `data/permissions` (tool permissions), `dryvist/claude-code-plugins` (commands,
skills, agents, hooks). Update the private docs site in the same session; most changes need it.
All delegated work routes per `model-delegation.md`: Codex on the newest Luna model at xhigh while `codex-quota` exits 0,
else the roster. Public coding, review and triage go to ZCode before the roster: load `delegation-ladder`
(`jpe-ai-delegation`) for the ladder, eligibility, and trusted PR verification.
Other orchestration and model routing: `model-delegation.md` (on-demand).
For bounded, routine subtasks, call `~/.agents/skills/fast-subagent/scripts/fast-subagent.sh` with `LLM_ROUTER_URL` and
`FAST_SUBAGENT_MODEL`; retain consequential judgment and decisions here.