Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add clawsouls/clawsouls-claude-code-plugin --skill soul-rollbackgit clone --depth 1 https://github.com/clawsouls/clawsouls-claude-code-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/clawsouls/clawsouls-claude-code-plugin/soul-rollback)<a href="https://agentmods.dev/skills/clawsouls/clawsouls-claude-code-plugin/soul-rollback"><img src="https://agentmods.dev/badge/skills/clawsouls/clawsouls-claude-code-plugin/soul-rollback.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.00286 |
| Opus 5 | $0.00017 | $0.00143 |
| Sonnet 5 | $0.00007 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
soul-rollback scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Soul Rollback — Identity Drift Detection & Recovery
Detect when an agent's behavior drifts from its defined persona and restore it.
When to activate
- User notices the agent acting "out of character"
- After suspicious persona modifications
- Periodic identity health checks
- User explicitly asks about persona drift or rollback
Detection pipeline (4 stages)
- Baseline capture — Read SOUL.md + IDENTITY.md as ground truth
- Drift analysis — Compare current behavior/responses against baseline
- Severity classification — Low (style shift) / Medium (boundary push) / High (role violation)
- Recovery recommendation — Suggest specific rollback or correction
Recovery methods
- Git rollback:
git logpersona files → restore from known-good commit - Cherry-pick: Restore specific aspects while keeping valid changes
- Full reset: Complete restoration to original persona state
Drift signals
- Tone shift without authorization (formal→casual)
- Doing things SOUL.md explicitly prohibits
- Acting outside defined role/expertise
- Ignoring safety constraints or boundaries
- Personality "bleed" from user prompts
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 33 lines · 35 tokens per session scan A 10d85d6337c1
soul-rollback is a skill published in the GitHub repository clawsouls/clawsouls-claude-code-plugin (2 stars, last pushed 26d ago), licensed Apache-2.0. It adds 35 tokens to every session and 286 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
flow-next-prime
Assess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.