Menu
Read-only inspection of the agentic-engineering activation resolver.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
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
| name | ds-status |
| description | Read-only inspection of the agentic-engineering activation resolver. |
| user-invocable | true |
Read-only inspection of the agentic-engineering activation resolver. Dumps the resolved global config, project marker, profile, and first-activation sentinel state. Writes nothing. Always exits 0.
Implementation: bin/agentic-status (Python 3 stdlib).
agentic-status
No subcommands, no flags. Reads:
~/.claude/agentic-engineering.json (global config)<cwd>/AGENTS.md (project marker; resolves through CLAUDE.md @AGENTS.md import if present)<cwd>/.agentic/.activated (first-activation sentinel)<cwd>/.agentic/config.json (project config; surfaces the deferred_wrap_daemon toggle - prints its value, or false when the file or key is absent)agentic-engineering status
global config: /Users/<you>/.claude/agentic-engineering.json (found)
mode: opt-out (source: global config)
profile: default (source: global)
set_at: 2026-04-15T12:00:00Z
project marker file: /path/to/project/AGENTS.md
marker: none
active: yes (mode=opt-out + marker=none -> active: opt-out activates everywhere unless a project opts out)
sentinel: .agentic/.activated (present)
deferred_wrap_daemon: false (source: .agentic/config.json; out-of-session daemon for deferred /ds-wrap jobs)
DEPRECATED example (only shown when a legacy preset key is present at some scope):
DEPRECATED: preset key 'strict' (global) resolved to profile=strict; migrate by setting
profile=strict directly - preset support will be removed after the deprecation window.
What this means
Active here: yes. The methodology governs how work gets done in this project.
Profile 'default': single-file behavioral edits run directly with a self-check;
multi-file changes, new files, shared utilities, config, and anything risky
spawn a Worker plus an independent Skeptic review.
(relaxed: single-file behavioral edits, small pure-UI multi-file changes, AND
bounded 2-3-file behavioral edits (connectivity-bound, <=30 changed lines,
zero other Elevated signals) run directly - lighter review, faster iteration.)
(strict: UI-copy tweaks, file renames, and targeted wording fixes are all treated
as Elevated and get Worker + Skeptic - broadest review coverage.)
How to adjust
Change the profile for THIS project:
add a line to /path/to/project/AGENTS.md: agentic-engineering-profile: relaxed (or default / strict)
Change the profile GLOBALLY:
edit /Users/<you>/.claude/agentic-engineering.json -> "profile": "relaxed" | "default" | "strict"
Turn the skill OFF for this project: /ds-disable
Turn it off EVERYWHERE: /ds-disable --global
See every command: /ds-help
Note: deleting the sentinel re-arms the first-activation notice only.
To opt out, use /ds-disable.
The source annotation on mode and profile records where
the effective value came from:
mode source: global config - the mode was read from a valid
~/.claude/agentic-engineering.json; global config (default; file missing)
mode falls back to its
opt-out default.global - the profile value comes from a valid profile: key in
~/.claude/agentic-engineering.json.project - the value comes from a valid agentic-engineering-profile:
line in AGENTS.md.global (legacy preset) - no valid profile key at global scope, but a
legacy preset: key resolved to this value via the deprecated preset
table (see the DEPRECATED notice, which fires on presence of the legacy
key regardless of whether it wins).project (legacy preset) - no valid agentic-engineering-profile: line
in AGENTS.md, but a legacy agentic-engineering-preset: marker resolved
to this value.global (default; unset) - nothing valid at any scope; falls back to the
hardcoded default..agentic/config.json - the deferred_wrap_daemon line comes from the
project config file; when the file or the key is absent, the line prints the
documented default (false).The active line carries the derivation that produced the active state -
the (mode=... + marker=... -> active|inactive: <reason>) clause - so it is
self-explanatory why the project is or is not governed. The "What this means"
block then explains the resolved profile's review behavior (with the other
two profiles shown as parenthetical contrast), and the "How to adjust" block
lists the exact edits to change the profile or turn the skill off. A
DEPRECATED line appears whenever a legacy preset key is present at either
scope, independent of whether it won resolution.
The .agentic/.activated sentinel is the per-project record that the
first-activation notice has already been shown. Deleting it re-arms the
notice only - it does NOT change activation state, the global config,
or the project marker. To actually opt the project out, use
/ds-disable.
0 - always. The command is read-only and never raises on missing or
malformed input. Missing config, missing AGENTS.md, and parse errors
all render as missing / none / defaults.