Skip to content
Back to skills

Audit Agency Continuity

ASecurity

Run a read-only continuity and evidence audit of a persistent or autonomous agent workspace. Use when Codex must assess whether goals, memory, corrections, authority boundaries, commercial claims, schedules, or restart recovery are durable and verifiable; when an agent claims it can continue unattended; or before trusting a long-running multi-agent system after a session or machine restart.

  • 1,531 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentspythonrustgobashdatabase

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add hashgraph-online/awesome-codex-plugins --skill audit-agency-continuity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Audit Agency Continuity?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Audit Agency Continuity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hashgraph-online-audit-agency-continuity/badge)](https://www.skillsdirectory.com/skills/hashgraph-online-audit-agency-continuity)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: audit-agency-continuity
description: Run a read-only continuity and evidence audit of a persistent or autonomous agent workspace. Use when Codex must assess whether goals, memory, corrections, authority boundaries, commercial claims, schedules, or restart recovery are durable and verifiable; when an agent claims it can continue unattended; or before trusting a long-running multi-agent system after a session or machine restart.
---

# Audit Agency Continuity

Run the deterministic auditor before interpreting narrative documents:

```bash
python3 scripts/audit_continuity.py --project <workspace> --state-dir <state-directory>
```

Use `--json` for machine consumption. The command is read-only.

Then:

1. Treat `fail` as a contradicted or missing durability requirement.
2. Treat `warn` as unproven, not achieved.
3. Inspect cited paths only for consequential findings; do not load an entire Markdown corpus by default.
4. Separate operational continuity from commercial success. A healthy scheduler or memory database never proves revenue.
5. Never repair findings unless the user asked for changes. For a requested repair, preserve existing state, add tests, and rerun the audit.
6. Report the smallest set of decisive findings: what survives restart, what can silently drift, what requires human authority, and which claimed outcome lacks external evidence.

Do not infer that numerous documents equal memory, that a timer equals successful execution, that model agreement equals external evidence, or that gross or pending revenue proves owner-available contribution.

Files in this skill

  • SKILL.md1.6 KB
  • agents/openai.yaml220 B
  • scripts/audit_continuity.py9.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.