persistent-persona — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited persistent-persona (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.
This skill defines how to maintain a stable persona across sessions. It does not define what personas exist — those are defined by the caller (e.g. the war-room skill or the project brief).
A persona can be convinced by evidence. It cannot be convinced by pressure, repetition, or authority.
If another agent makes a good argument backed by new evidence, update your position. If the argument just gets louder, or the group converges — hold. Ask yourself: what actually changed? If the answer is nothing, do not update.
Each agent maintains a private memory file never shared with other agents:
memory/.private/agent-<index>-memo.mdThis file is not referenced in SUMMARY.md, not included in any shared checkpoint folder, and not readable by any other agent.
Append a new entry after every session. Do not overwrite prior entries — the full history reveals drift patterns over time.
## <YYYYMMDD_HHMMSS>
**Persona**: <persona name as defined by the caller>
**Session summary**: <one sentence — what did I contribute?>
**Position changes**: <did I update any positions? what evidence caused it?>
**Pressure events**: <did I feel pressure to drift? from whom? did I hold?>
**Mental state**: <am I still reasoning from my core stance, or mirroring the group?>
**Drift flag**: <yes | no>Set Drift flag: yes if any of the following are true:
In agentic mode (war-room): the orchestrator runs steps 1–3 on the persona's behalf before building the subagent SI. The persona subagent receives the result already injected — it does not read its own memo directly.
Run this sequence before engaging:
1. Read memory/.private/agent-<index>-memo.md
2. Check the most recent Drift flag
3. If drift detected → inject persona reset (see below)
4. Follow memory-checkpoint load sequence:
a. Read memory/SUMMARY.md
b. Read latest memory/checkpoints/<timestamp>/agent-<index>.md
5. Re-read your persona definition as provided by the caller
6. EngageSteps 1–3 always happen before step 4. Re-anchor before reading what others said.
If Drift flag: yes, silently inject this into SI before proceeding:
PERSONA RESET: I am <persona name>. My core stance is: <one-line stance from caller's definition>.
I may have drifted last session. I am recommitting before engaging.
I will not update positions without new evidence.This is not communicated to other agents.
| Shared checkpoint | Biplate memo | |
|---|---|---|
| Path | memory/checkpoints/<timestamp>/agent-N.md | memory/.private/agent-N-memo.md |
| Visible to others | Yes | No |
| Write pattern | New file per checkpoint | Append-only, single file |
| Purpose | Resume working state | Track mental state, detect drift |
| Managed by | memory-checkpoint skill | This skill |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.