Menu
Append the agentic-engineering opt-out marker to the project
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Apply when the user mentions any software development work: implementing features, fixing bugs, reviewing or refactoring code, debugging, testing, deploying, working with agents or subagents, making architecture decisions, setting up projects, managing dependencies, writing scripts, or any task that involves reading, writing, or reasoning about code and systems.
Agentic Engineering Protocol for Hermes - structured delegation model, risk classification, adversarial review loops, code quality gates, git workflow conventions, and named agent definitions. Load this skill when doing AI-assisted software development with Hermes Agent.
Apply when the user mentions any software development work: implementing features, fixing bugs, reviewing or refactoring code, debugging, testing, deploying, working with agents or subagents, making architecture decisions, setting up projects, managing dependencies, writing scripts, or any task that involves reading, writing, or reasoning about code and systems.
Pre-implementation technical design agent. Spawn when you need a structured technical plan before writing code. Reads the codebase, identifies patterns and constraints, evaluates approaches, and produces a concrete plan a Worker can execute directly. Never writes or modifies files.
General-purpose implementation agent. Spawn for any code change: new features, bug fixes, refactors, configuration changes, or script writing. Reads the codebase to understand conventions, implements the change, runs quality gates, and returns a clear summary of what was done. This is the standard Worker for all Elevated-risk implementation tasks.
Cheap per-turn stop-condition check for open-goal loops. Spawned by the conductor ONLY after an Elevated iteration produces a clean Skeptic sign-off, to evaluate the operator-declared goal_condition and return continue-vs-stop only - never for a Low/Trivial iteration (no Skeptic sign-off exists to run after; the conductor evaluates goal_condition directly there instead). Tier 1 (haiku) leaf agent - read-only, no subagent spawning, never runs in place of, before, or concurrently with a Skeptic review. Does NOT review correctness or safety and does NOT raise, waive, or comment on Skeptic findings. Returns BLOCKED only as a structural guard when spawned without a confirmed Skeptic sign-off; the conductor handles this BLOCKED as a fallback to direct evaluation, NOT as the generic Worker-BLOCKED-means-cap_reached-escalation semantics in content/references/subagent-protocol.md - a BLOCKED return here never halts the loop. On any other failure (unavailable, errored, timeout, malformed output) the conductor falls bac
Basé sur la classification professionnelle SOC
| name | ds-disable |
| description | Append the agentic-engineering opt-out marker to the project |
| user-invocable | true |
Append the agentic-engineering opt-out marker to the project
AGENTS.md (creating it if absent). Optionally also updates the global
config. Refuses to overwrite an existing opt-in marker without
--force.
Implementation: bin/agentic-disable (Python 3 stdlib).
agentic-disable # write opt-out to project AGENTS.md
agentic-disable --global # also update ~/.claude/agentic-engineering.json
agentic-disable --force # remove existing opt-in marker first, then append opt-out
agentic-disable --global --force
The script resolves the project AGENTS.md (following CLAUDE.md
@AGENTS.md import if present) and:
AGENTS.md contains a whole-line
agentic-engineering: opt-in (case-insensitive, optional -
prefix), the command exits non-zero (exit code 2) without modifying
any file. The error message names the absolute path and line number
of the existing marker. Pass --force to remove the opt-in line
first, then append opt-out.AGENTS.md already contains a whole-line
agentic-engineering: opt-out, the command is a no-op (exit 0)
and prints the existing marker location.\n\n or empty: append agentic-engineering: opt-out\n.\n but not \n\n: append \nagentic-engineering: opt-out\n.\n: append \n\nagentic-engineering: opt-out\n.
Atomic write via tmp + rename - partial writes cannot leave
AGENTS.md corrupted.AGENTS.md does not exist,
the script creates it with a single line: agentic-engineering: opt-out\n.
Rationale: the user invoked /ds-disable, an explicit opt-out
signal; creating AGENTS.md with the marker is the
minimum-blast-radius way to record that intent.--globalUpdates ~/.claude/agentic-engineering.json with mode=opt-out and a
fresh set_at ISO8601 UTC timestamp. Preserves existing keys
verbatim: the helper writes back the same set of keys it read; absent
keys remain absent. The script will not invent any key not already
present in the file.
If the config file is missing, it is created with the minimal shape
{"mode": "opt-out", "set_at": "<iso>"}.
--forceWhen an agentic-engineering: opt-in line is present in AGENTS.md,
--force removes the entire line (including its trailing newline,
leading whitespace, and any - list prefix) before appending the
opt-out marker. The removed line is recoverable via git. The
confirmation output prepends a --force: removed existing 'opt-in' marker at line <N>. line to the standard write summary.
0 - success or idempotent no-op1 - I/O error (read-only filesystem, permission denied, etc.)2 - opt-in conflict and --force was not passed; no files modified/ds-disable is reversible: the marker is one line in a tracked
file, and the JSON edit is round-trippable. --force is also
reversible because the removed opt-in line is recoverable from git.
The command is direct-action eligible - no extra confirmation prompt.