create audit agent

Security Community

Skill notes

Examples

/create-audit-agent my-data-expert -- create a new agent /create-audit-agent audit my-data-expert -- audit a specific agent /create-audit-agent audit all -- audit all agents with summary table

Mode Selection

Parse $ARGUMENTS: audit, audit <name>, or audit all → Audit mode Anything else (name, description, or empty) → Create mode CREATE MODE Five phases: Gather → Reference → Generate → Register → Verify.

1a. Scan existing agents

List all .md files in .claude/agents/ to prevent name collisions and understand existing scope.

1b. Ask the user

If $ARGUMENTS contains a name or description, use it. Otherwise, use AskUserQuestion with all of the following: Name: lowercase-with-hyphens identifier (e.g., my-data-expert) Purpose: What domain does this agent cover? What databases, tables, or APIs does it work with? Key routing terms: What keywords should trigger delegation? (database names, table names, acronyms, paper names) Tools needed: What tools should the agent have? (read-only vs full access, specific tools)

1c. Skill vs Agent decision

Before proceeding, ask: "Is this a known, rigid workflow with fixed inputs?" If yes, recommend a skill (/create-skill) instead. Agents are for tasks requiring judgment, discovery, or error recovery. Skills run in the caller's context with zero spawn overhead (75-80% fewer tokens). See docs/AGENT_LESSONS_LEARNED.md for rationale.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Gather Requirements

Phase 1: Gather Requirements

02
Phase 2: Generate

Build the agent `.md` file: Frontmatter: Description requirements: Include 3+ `<example>` blocks with realistic user queries, assistant responses, and `<commentary>` Include ALL key routing keywords: database names, table names, schema names, acronyms

03
Phase 3: Register

Phase 3: Register

04
Phase 4: Verify

Run the full 17-point audit checklist (from Audit Mode below) against the new agent. Report results. Fix any FAIL items before considering the skill complete. AUDIT MODE Four phases: Read → Analyze → Report → Fix.

05
Phase 1: Read

Parse the audit target from `$ARGUMENTS`: `audit <name>` → read `.claude/agents/{name}.md` `audit all` → list and read all `.md` files in `.claude/agents/` `audit` (no target) → list all agents as a numbered list, ask which to audit (or offer `all`) Also read:

06
Phase 2: Analyze

Run 17 checks grouped in 5 categories. For each: PASS, WARN, or FAIL.

07
Phase 3: Report

Print structured report: For `all` mode, print each agent's report separately, then a summary table:

08
Phase 4: Fix (Optional)

After reporting, offer to fix FAIL items: "Would you like me to fix the {N} FAIL items? I'll show each proposed change before applying." A4/B7 (routing keywords): propose updated description with missing terms added D14 (CLAUDE.md): propose adding agent to specialist section D15 (orchestrator): propose adding row to dispatch table

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.