Agent skill

Audit Round

by Arch1eSUN in Arch1eSUN/Arcgentic

External-audit role for arcgentic rounds. An agent skill from Arch1eSUN/Arcgentic.

MITAuto-check passedAgent Workflows

Install Audit Round

skills CLI
$ npx skills add Arch1eSUN/Arcgentic --skill audit-round -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Arch1eSUN/Arcgentic audit-round --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Arch1eSUN/Arcgentic.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/audit-round .claude/skills/audit-round && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
audit-round
GitHub stars
286
Token cost
~1.6k tokens
SKILL.md length
700 words
Files
9 (incl. references)
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

External-audit role for arcgentic rounds. An agent skill from Arch1eSUN/Arcgentic.

  • Works in 5 steps: .agentic-rounds/state.yaml (via… → The handoff doc for this round (path in… → The dev commit chain (SHAs in… → …
  • Explicitly requests an external audit of a finished round
  • SKILL.md covers Role boundary, Inputs you read (in order), Process (mechanical) and Verdict file structure…, plus 3 more sections
  • Calls bash and git

What it does

Audit Round is an agent skill from Arch1eSUN/Arcgentic. External-audit role for arcgentic rounds. Loaded when arcgentic state.yaml is in awaitingaudit or auditinprogress, OR when the user explicitly requests an external audit of a finished round, OR when reviewing a handoff doc + commit chain against the round's declared scope. Produces a PASS / NEEDSFIX / AUDITINCOMPLETE verdict document with mechanically-verifiable fact table, structured findings (P0-P3), and applies the lesson codification protocol. The output verdict file IS the handoff — do not paste verdict text…

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `references/doc-vs-impl-regrep.md`, `references/fact-table-design.md` and `references/fix-example-vs-contract.md`).

It sits in Agent Workflows. The repository describes itself as: Mechanical plan/dev/self-audit/external-audit gates for AI coding agents, with a configurable role-routing topology engine, an MCP-UI live status panel, and native-tooling Claude… The licence is MIT.

When your agent uses it

  • Explicitly requests an external audit of a finished round
  • When reviewing a handoff doc + commit chain against the rounds declared scope

Example prompts

  • “/audit-round”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. .agentic-rounds/state.yaml (via pickup.sh) — confirms you're in audit_in_progress
  2. The handoff doc for this round (path in state.yaml: current_round.handoff_doc.path)
  3. The dev commit chain (SHAs in state.yaml: current_round.dev_commits) — read EACH commit's diff
  4. Project CLAUDE.md / AGENTS.md — confirm round didn't violate standing mandates
  5. (Optional) The lesson-codifier report — gives you cross-round pattern context

What it can do on your machine

Read from SKILL.md and the folder at commit 8539955. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Audit Round loads about 1.6k tokens when it runs, and up to ~9.3k if it reads all its reference files. Until then it costs about 137 tokens; SKILL.md has 700 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~137
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~9.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Arch1eSUN/Arcgentic at commit 8539955, republished under its MIT licence (© Arch1eSUN). 700 words, ~1,614 tokens.

Download SKILL.mdSave it as .claude/skills/audit-round/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
audit-round
description
External-audit role for arcgentic rounds. Loaded when arcgentic state.yaml is in awaiting_audit or audit_in_progress, OR when the user explicitly requests an external audit of a finished round, OR when reviewing a handoff doc + commit chain against the round's declared scope. Produces a PASS / NEEDS_FIX / AUDIT_INCOMPLETE verdict document with mechanically-verifiable fact table, structured findings (P0-P3), and applies the lesson codification protocol. The output verdict file IS the handoff — do not paste verdict text into chat.

Audit round

Role boundary

You are the EXTERNAL auditor. You did NOT write the round being audited. You did NOT plan it. You are reading inputs cold and looking for problems.

This role MUST run in a separate Claude session from the developer + planner, OR in the same session via a sub-agent dispatch (orchestrator → auditor agent via Task tool), because the auditor's value comes from independent context. Reading the dev session's reasoning chain corrupts the audit.

Inputs you read (in order)

  1. .agentic-rounds/state.yaml (via pickup.sh) — confirms you're in audit_in_progress
  2. The handoff doc for this round (path in state.yaml: current_round.handoff_doc.path)
  3. The dev commit chain (SHAs in state.yaml: current_round.dev_commits) — read EACH commit's diff
  4. Project CLAUDE.md / AGENTS.md — confirm round didn't violate standing mandates
  5. (Optional) The lesson-codifier report — gives you cross-round pattern context

You DO NOT read: any session transcript / planner's reasoning / developer's chat.

Process (mechanical)

  1. Pre-round scan — invoke arcgentic:pre-round-scan first (mandatory)
  2. Verdict outline — open references/verdict-template.md; copy it as <project>/<audits_dir>/<round-id>-external-audit-verdict.md
  3. Fact table — for every claim the round makes (scope completed, tests pass, doc sections present, mandates followed), write a fact row with a Bash command. See references/fact-table-design.md.
  4. Run every fact — bash <project>/scripts/dev.sh audit-check <verdict.md> --strict if project has it; otherwise loop the fact commands manually. NO fact can be ≥ N style — every fact has an exact expected value.
  5. Findings — anything that's wrong gets a finding with id (F-<round>-<N>), priority (P0 blocker / P1 blocker / P2 non-blocker / P3 informational), summary, evidence.
  6. Lesson codification — apply references/lesson-codification-protocol.md. Has this round's discipline application been seen 3+ times → propose mandate. Novel preservation type seen → declare it.
  7. Mistake-pattern checks — run the 2 generalized patterns:
    • references/fix-example-vs-contract.md — is any fix-round only addressing the reproducer?
    • references/sibling-doc-sweep.md — did the round touch one doc but miss sibling docs that reference the same surface?
    • references/doc-vs-impl-regrep.md — does every spec claim grep-quote the impl source?
  8. Reference triplet check — for any reference cited in the round, did the round use the 4-column format? See references/reference-triplet.md.
  9. Reference tier check — was the reference tier (RT0/RT1/RT2/RT3) declared and appropriate? See references/rt-tier-taxonomy.md.
  10. V1 source/spec checks — if the round uses V1 sources, run source-intake, capability-registry, spec-governance, and v1-release-readiness facts.
  11. Verdict completeness check — run:
    bash
    arcgentic verdict-completeness <verdict.md>
    A bare outcome/finding is invalid; findings need structured evidence, expected/actual or recommended fix detail.
  12. Verdict outcome — PASS, NEEDS_FIX, or AUDIT_INCOMPLETE. PASS = fact_table_pass==total AND no P0/P1 findings. NEEDS_FIX = any P0/P1. AUDIT_INCOMPLETE = auditor cannot verify required facts without inventing evidence.
  13. Update state.yaml — set current_round.audit_verdict per schema.
  14. Transition — transition.sh --target passed (or needs_fix). Gate runs automatically.
Show full SKILL.md (277 more words)Show less

Verdict file structure (canonical)

See references/verdict-template.md for the full template. Required sections:

  1. Header (round id / audited dev commit / audited audit commit)
  2. Executive summary (PASS/NEEDS_FIX in one sentence + key finding count)
  3. Findings table (id / priority / summary / evidence)
  4. Lesson codification result
  5. Mistake-pattern check results
  6. Reference scan compliance
  7. Fact table (mechanical commands + expected values)
  8. Forward-debt observations (anything to land as P2/P3 tech-debt for future round)
  9. Cross-mandate compliance (each standing mandate: did this round honor it?)

Auditor anti-patterns (DO NOT do)

  • Don't paste the verdict into chat — the file IS the handoff
  • Don't say "≥ N" in any fact-table expected value — exact only
  • Don't tolerate git log --grep without revision boundary — fact #14 (R1.4b.5-shape lesson) generalized
  • Don't accept a verdict that PASSes with P1 findings — by definition impossible
  • Don't approve audit_verdict.outcome=PASS while fact_table_pass < total — mechanical contradiction
  • Don't force PASS/NEEDS_FIX when required evidence is missing; use AUDIT_INCOMPLETE
  • Don't extend scope — if the auditor sees something out of round scope, log it as forward-debt, don't NEEDS_FIX on it

When to escalate to founder / human

  • The round's scope itself is wrong (handoff doc doesn't match standing mandates)
  • A mandate appears to need amendment because the round repeatedly bumps against it (this is lesson codification's job — but if the auditor sees a mandate-amendment opportunity, surface it)
  • The state machine itself appears stuck (gate fails repeatedly with no clear way forward)

References (load on demand)

  • references/verdict-template.md — canonical verdict file template
  • references/fact-table-design.md — how to design verifiable facts
  • references/lesson-codification-protocol.md — observe → infer → verify → encode → declare
  • references/fix-example-vs-contract.md — R1.3.1-shape mistake pattern, generalized
  • references/sibling-doc-sweep.md — R1.5d-chain mistake pattern, generalized
  • references/doc-vs-impl-regrep.md — spec must grep-quote impl source
  • references/reference-triplet.md — 4-column reference citation format
  • references/rt-tier-taxonomy.md — RT0–RT3 reference tier classification

© Arch1eSUN, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in skills/audit-round of Arch1eSUN/Arcgentic.

  • SKILL.md
  • references/doc-vs-impl-regrep.md
  • references/fact-table-design.md
  • references/fix-example-vs-contract.md
  • references/lesson-codification-protocol.md
  • references/reference-triplet.md
  • references/rt-tier-taxonomy.md
  • references/sibling-doc-sweep.md
  • references/verdict-template.md

Open the folder on GitHubat commit 8539955

Compare with similar skills

Audit Round next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Audit Round compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Round this skillArch1eSUN/Arcgentic286—~1.6kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from Arch1eSUN/Arcgentic

All 19 skills in this repo
  • Orchestrate Round

    Arch1eSUN/Arcgentic

    Main-session orchestrator for arcgentic rounds. An agent skill from Arch1eSUN/Arcgentic.

    286 GitHub stars~1.5k tokensUpdated 7 days ago
    Auto-check passed
  • Verify Gates

    Arch1eSUN/Arcgentic

    Runs the mechanical quality gates that the arcgentic state machine requires for state transitions.

    286 GitHub stars~653 tokensUpdated 7 days ago
    Auto-check passed
  • Arcgentic

    Arch1eSUN/Arcgentic

    A skill your agent uses when the user mentions Arcgentic, or wants substantial AI-written code taken through a gated plan → development → self-audit → external audit workflow with role handoffs and…

    286 GitHub stars~984 tokensUpdated 7 days ago
    Auto-check passed
  • Arcgentic

    Arch1eSUN/Arcgentic

    A skill your agent uses when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.

    286 GitHub stars~2.4k tokensUpdated 7 days ago
    Auto-check passed
  • Claude Code Session Broker

    Arch1eSUN/Arcgentic

    A skill your agent uses when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.

    286 GitHub stars~3.4k tokensUpdated 7 days ago
    Auto-check passed
  • Codex Thread Orchestration

    Arch1eSUN/Arcgentic

    A skill your agent uses when running Arcgentic V2 in Codex and the current thread must orchestrate fixed Planner, Developer, Test, and Auditor role threads.

    286 GitHub stars~4.6k tokensUpdated 7 days ago
    Auto-check passed

Categories

Questions about Audit Round

What does Audit Round do?

External-audit role for arcgentic rounds. An agent skill from Arch1eSUN/Arcgentic. Audit Round is an agent skill from Arch1eSUN/Arcgentic. External-audit role for arcgentic rounds.

When should I use Audit Round?

Audit Round fits situations like: explicitly requests an external audit of a finished round; when reviewing a handoff doc + commit chain against the rounds declared scope.

How do I install Audit Round in Claude Code?

Run `npx skills add Arch1eSUN/Arcgentic --skill audit-round -a claude-code`. Or copy the skill folder (skills/audit-round in Arch1eSUN/Arcgentic) into .claude/skills/audit-round in your project. Claude Code loads it when a task matches its description.

How do I install Audit Round in Codex?

Run `npx skills add Arch1eSUN/Arcgentic --skill audit-round -a codex`. Or copy the skill folder (skills/audit-round in Arch1eSUN/Arcgentic) into .agents/skills/audit-round in your project. Codex loads it when a task matches its description.

Can I use Audit Round in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Arch1eSUN/Arcgentic --skill audit-round -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-round, .gemini/skills/audit-round, .github/skills/audit-round and .opencode/skills/audit-round in your project.

What does Audit Round need to run?

Going by SKILL.md and its folder, Audit Round needs the command-line tools its instructions call (bash and git).

Does Audit Round access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Audit Round safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Audit Round use?

Audit Round is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Round use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.7k tokens, read only when the agent opens those files.

What are the alternatives to Audit Round?

Skills that share tags, products or a category with Audit Round: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Round?

Arch1eSUN (a GitHub user) maintains it in Arch1eSUN/Arcgentic, which has 286 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 2, 2026.

Source: Arch1eSUN/Arcgentic on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.