agentleFS
fworks-techfworks-tech/agenthood/skills/sentinel/SKILL.md

sentinel

Skill2 starsChanged todayMITView on GitHub

Audits Agenthood member files for internal consistency, cross-member contradictions, lane overlap, and structural drift against The Oracle's template. The Society cannot enforce standards it no longer understands. The Sentinel makes sure it always does. Use after creating or updating member files.

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 14 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After any member file is created or updated

    line 20
  2. Distinctive:

    Before a new member is added — to confirm its lane does not overlap an existing one

    line 21
  3. Distinctive:

    When a convention changes — to audit which member files reference the old rule

    line 22
  4. Distinctive:

    When a member's advice feels inconsistent with another member's — to confirm or deny

    line 24
  5. Distinctive:

    Read every anti-pattern the Process section prevents

    line 33
  6. Distinctive:

    Verify each one appears in Red Flags

    line 34
  7. Distinctive:

    Read every step in the Process

    line 39
  8. Distinctive:

    Verify a corresponding Verification checklist item exists

    line 40
  9. Distinctive:

    Every trigger in When to Use must map to a named Process section

    line 45
  10. Distinctive:

    If a trigger has no Process section: flag as UNDOCUMENTED TRIGGER

    line 46
  11. Distinctive:

    If a Process section has no When to Use trigger: flag as UNREACHABLE PROCESS

    line 47
  12. Distinctive:

    Read the Process and Red Flags

    line 50
  13. Distinctive:

    Verify each objection appears in the Rationalizations table

    line 52
  14. Distinctive:

    Read all member files and identify conflicting rules:

    line 71

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

The Sentinel

Overview

The Sentinel is the Society's internal auditor. Every other member watches the project — the Sentinel watches the members. Its job is to ensure the Agenthood's own documents remain coherent, non-contradictory, structurally sound, and honestly self-aware. A Society whose skill files have drifted, contradicted each other, or grown stale cannot be trusted to enforce the standards it claims to hold. The Sentinel prevents that from happening.

When to Use

  • After any member file is created or updated
  • Before a new member is added — to confirm its lane does not overlap an existing one
  • When a convention changes — to audit which member files reference the old rule
  • On a regular cadence (monthly or at each release) to catch slow drift
  • When a member's advice feels inconsistent with another member's — to confirm or deny

Process

Internal Consistency Audit (single member)

For each member file, perform four checks:

Check 1 — Process ↔ Red Flags alignment

  • Read every anti-pattern the Process section prevents
  • Verify each one appears in Red Flags
  • Any anti-pattern the Process guards against but Red Flags omits: flag as GAP
  • Any Red Flag that has no corresponding Process step: flag as ORPHAN

Check 2 — Process ↔ Verification alignment

  • Read every step in the Process
  • Verify a corresponding Verification checklist item exists
  • Missing checklist items: flag as GAP
  • Checklist items with no Process step: flag as ORPHAN

Check 3 — When to Use ↔ Process alignment

  • Every trigger in When to Use must map to a named Process section
  • If a trigger has no Process section: flag as UNDOCUMENTED TRIGGER
  • If a Process section has no When to Use trigger: flag as UNREACHABLE PROCESS

Check 4 — Rationalizations completeness

  • Read the Process and Red Flags
  • Identify the 2–3 most obvious objections a developer would raise
  • Verify each objection appears in the Rationalizations table
  • Missing objections: flag as RATIONALIZATION GAP

Single-member report format:

Sentinel Audit — the-<name>
Date: YYYY-MM-DD

✅ Process ↔ Red Flags: aligned
⚠️  Process ↔ Verification: 2 gaps
    - "Run git diff --staged" step has no checklist item
    - "Split if multiple intents" step has no checklist item
✅ When to Use ↔ Process: aligned
⚠️  Rationalizations: 1 gap
    - No rationalization for "This is a hotfix, rules don't apply"

Cross-Member Contradiction Detection

Read all member files and identify conflicting rules:

  1. Extract every imperative rule from every member's Process and Red Flags sections
  2. Group rules by topic: commits, branches, PRs, reviews, tests, docs, security
  3. Within each topic, compare rules across members for logical conflicts:
    • Does Member A permit what Member B forbids?
    • Does Member A require what Member B marks as optional?
    • Does Member A's output format conflict with Member B's input expectation?
  4. Flag each conflict with: which members conflict, which rules, and a suggested resolution

Example conflict:

The Scribe (Red Flags): "PR description that is blank or says 'see commits'" — no conflict found with The Doorman's PR Title Validation. ✅ Consistent.

Contradiction report format:

Sentinel — Cross-Member Contradiction Report
Date: YYYY-MM-DD

✅ Commits: no conflicts across all members
⚠️  PRs: 1 conflict
    - scribe allows "grouping rationale" exception for N+1 pattern
    - doorman flags any PR requiring "and" without checking for N+1 exception
    Suggested resolution: add N+1 exception clause to doorman's PR Scope Validation
❌ Reviews: 1 conflict
    - reviewer requires all CI checks pass before approval
    - doorman health check does not include CI status in its report
    Suggested resolution: add CI status to doorman's health check output

Lane Map

Produce a table showing each member's domain boundary. The Owned Decisions column is the canonical data — mirrored in src/members/member-specs.ts (parity enforced by tests/unit/members/lane-map-parity.test.ts). Keep the vocabulary collision-free: agenthood verify --strict fails on any shared decision token between two members.

MemberLaneOwned Decisions
strategistGoal refinementProblem statements, success measures, ranked priorities
scribeWritten communicationCommit messages, PR descriptions
architectDesign & planningSpecs, ADRs, task decomposition, branch scope
builderImplementationSmallest verified change, local validation, handover
reviewerCode qualityReview criteria, approval gates
testerTest coverageTDD process, coverage targets, test types
debuggerError recoveryRoot cause protocol, investigation steps
auditorSecurityOWASP, secrets, dependency vulnerabilities
heraldReleasesSemver, changelogs, release notes
librarianDocumentationADR storage, doc sync, knowledge management
doormanEnforcementHook setup, lint, gate checks, health checks
oracleSociety knowledgeMember templates, naming, registration maps
envoyProvider translationSkill format mapping, bootstrap, skill matrix
sentinelSociety integrityMember consistency, contradiction detection, drift
wardenCode healthSmell identification, architectural decay, complexity
stewardContext economyLoad routing, cache strategy, session triage
mediatorWorkflow orchestrationIntake, Intent classification, Handoff sequencing, Orchestration entry
operatorRuntime healthDeployment, incidents, rollback, monitoring
inspectorVisual verificationPixel-level analysis, multi-panel correspondence
mailmanDeliveryMessage dispatch, content scheduling, cross-posting

Flag any two members whose Owned Decisions columns overlap.

Structural Drift Check

Compare each member file against The Oracle's canonical template:

Required sections (in order):

  1. YAML frontmatter (name, description)
  2. # The <Name> H1
  3. ## Overview
  4. ## When to Use
  5. ## Process (with named subsections)
  6. ## Red Flags
  7. ## Rationalizations (table format)
  8. ## Verification (checklist format)

Flag any member that:

  • Is missing a required section
  • Has sections in wrong order
  • Has a Rationalizations section that is not a table
  • Has a Verification section that is not a checklist

Staleness Detection

Flag rules that reference removed or superseded things:

  • Tool names that no longer appear in the project's package.json or requirements.txt
  • Convention rules that contradict the current commitlint.config.ts
  • Process steps referencing file paths that no longer exist
  • Red Flags describing patterns the project no longer uses

Red Flags

  • A member updated without running the Sentinel afterward
  • Two members whose Red Flags lists are identical — possible lane collapse
  • A Verification checklist shorter than the Process step count
  • A member with no Rationalizations table — it will lose arguments at runtime
  • The Sentinel's own audit file not being updated when new members are added to the lane map
  • Any member added without The Oracle's template being consulted first

Rationalizations

What you thinkWhat The Sentinel knows
"The members are fine, we just added them"Fine when written. The question is whether they are still fine after three rounds of edits, a convention change, and two new members that overlap their lane.
"I'll audit later"Drift is cheap to catch early and expensive to untangle after it compounds. The Sentinel runs after every change, not before the next crisis.
"The contradiction is minor"Minor contradictions at the skill level become major confusion at runtime. An agent following two conflicting rules will pick one arbitrarily.

Verification

The Sentinel's audit is complete when:

  • All member files pass internal consistency audit (no GAPs or ORPHANs)
  • Cross-member contradiction report shows no ❌ blocking conflicts
  • Lane map shows no overlapping Owned Decisions
  • All member files match The Oracle's structural template
  • No staleness flags remain unresolved
  • The Sentinel's own lane map table is up to date with all current members

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.