agent-config — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited agent-config (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
guildmaster is the mesh's skills supplier and owns the inventory surfaces: "what kit + config does this agent have?" This skill answers exactly that for a single agent, showing the three artifacts that together define it:
CLAUDE.md / AGENTS.md / GEMINI.md) — theprompt-side guidance for the agent's backend. The script detects which file is present from a backend-fingerprint registry.
agents: list with suffix,backend, model, system_prompt, channels, tags, acp_command, extras). Lives parallel to the prompt file at the project root.
invoke, one line each (name + truncated description).
This is the inventory half of the steward → guildmaster split (issue #12): it reports the config, it does not interpret drift or judge alignment. The relationship graph and the "is this agent aligned?" judgment stay with steward overview / steward doctor.
guild teach / guild onboard — see an agent's current kit + config.<name>" or "what does <agent> run".One script, two ways to call it (or just run guild show, which wraps it):
# Path mode — point at any directory with a prompt file + culture.yaml
.claude/skills/agent-config/scripts/show.sh ../culture
# Suffix mode — resolve a registered agent suffix via the Culture server's
# manifest (location set by culture_server_yaml in skills.local.yaml)
.claude/skills/agent-config/scripts/show.sh dariaOutput is three sections: the detected system-prompt file, culture.yaml (or (missing)), and a one-line summary per local skill (name + description, truncated to 120 chars).
culture.yaml| Field | Why it matters |
|---|---|
suffix | Identifies the agent on the mesh. |
backend | One of claude / codex / copilot / acp. The all-backends rule means a feature in one must land in all four. |
model | Drift here changes behavior silently. |
system_prompt | Should not contradict the prompt file. |
channels | Where the agent listens. |
tags, extras, acp_command | Backend-specific. |
flag or fix drift — that judgment is steward's lane.
data/backend-fingerprints.yaml (the prompt: mapping), falling back to the built-in (CLAUDE.md AGENTS.md GEMINI.md) list if the registry is absent.
culture_server_yaml from.claude/skills.local.yaml (git-ignored), falling back to .claude/skills.local.yaml.example.
agent-config). guildmaster owns this copy and maydiverge; re-sync from steward's canonical copy when it changes. Divergences: the SKILL.md is reframed for guildmaster's inventory role and adds type: command for the culture backend's skill loader.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.