The description contains "great DX: intuitive command design". A bare colon in
an unquoted YAML scalar starts a mapping, so the parser fails the whole block
with "mapping values are not allowed in this context" and the agent is dropped
at load time.
Consumers see this. Agency Agents logs it on every launch:
WARN agency_agents_lib::corpus: corpus: engineering-developer-tooling-engineer:
frontmatter YAML parse error: mapping values are not allowed in this context
at line 2 column 132
Quoting rather than rewording, to match how the two other descriptions carrying
a colon are already handled — the text is the author's and reads correctly.
#778 fixed this class in convert.sh; this file predates that and was never
regenerated.
Verified: scripts/lint-agents.sh passes on the file, all 258 agent files parse
under yaml.safe_load, and the warning no longer appears on app startup.
Consolidates five gated PRs into one merge (each edited the README roster,
so landing individually would cascade conflicts):
- Security: AI-Generated Code Security Auditor, Secrets & Credential Hygiene
Engineer (#647, #648 — @Synvoya)
- Engineering: Database Reliability, Developer Tooling, IoT Fleet Engineer
(#705 — @Hotragn)
- Specialized: Codebase Archaeologist (#681 — @Axion-Web-dev)
All six cleared the full gate: lint 0/0, originality 0.0-0.1% (no dupes vs
roster or each other), proper structure, valid divisions. Roster rows added
to the Security/Engineering/Specialized tables (every link verified). Full
guard suite green — divisions, tools, runbooks, and the Hermes plugin guard —
and the Hermes roster picks up all six (254 -> 260 agents).
Claude-Session: https://claude.ai/code/session_01WKnDRWM4izsB8WAXKszhsq
Co-authored-by: Synvoya <Synvoya@users.noreply.github.com>
Co-authored-by: Hotragn <Hotragn@users.noreply.github.com>
Co-authored-by: Axion-Web-dev <Axion-Web-dev@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
John W. O'Grady
