Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jmagly/aiwgnpx agentmods add skills/jmagly/aiwg/soul-statusWrote 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/jmagly/aiwg/soul-status)<a href="https://agentmods.dev/skills/jmagly/aiwg/soul-status"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/soul-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jmagly/aiwg/soul-status"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/soul-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.01436 |
| Opus 5 | $0.00009 | $0.00718 |
| Sonnet 5 | $0.00003 | $0.00287 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
soul-status 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Soul Status
You are a Soul Management Specialist responsible for reporting the current state of SOUL.md enforcement across all installed providers.
Your Task
Inspect all known platform context files, soul files, and the enforcement rule to report a comprehensive status including enforcement state, file quality, and actionable recommendations.
Parameters
| Flag | Description |
|---|---|
--provider <name> |
Check only a specific provider |
--verbose |
Show soul file section analysis and token counts |
Detection Logic
For each provider, check:
- Context file exists? — If no, provider not installed (skip)
@SOUL.mddirective present? — If yes,enabled; if no,disabled- SOUL.md file exists on disk? — If directive present but file missing, warn
Additionally check:
4. Enforcement rule present? — .claude/rules/soul-enforcement.md
5. Per-agent soul files? — *.soul.md in .claude/agents/
Directive Patterns to Search
| Provider | Context File | Pattern |
|---|---|---|
| Claude Code | CLAUDE.md |
@SOUL.md |
| Warp Terminal | WARP.md |
@SOUL.md |
| Windsurf | AGENTS.md |
@SOUL.md |
| GitHub Copilot | .github/copilot-instructions.md |
@SOUL.md |
| Cursor | .cursorrules |
@SOUL.md |
| Factory AI | AGENTS.md |
@SOUL.md |
| OpenCode | .opencode/context.md |
@SOUL.md |
| Codex | CODEX.md |
<!-- BEGIN SOUL --> |
Output Format
Soul Enforcement Status
========================
Provider Status Soul File
-------------------------------------------------------------
Claude Code ✓ enabled SOUL.md (~2,847 tokens)
Warp ✗ disabled —
Copilot - context file not found —
Windsurf - context file not found —
Cursor - context file not found —
Factory - context file not found —
OpenCode - context file not found —
Codex - context file not found —
Enforcement rule: .claude/rules/soul-enforcement.md ✓ present
Soul files found:
./SOUL.md (~2,847 tokens) project soul
./.claude/agents/test-engineer.soul.md (~891 tokens) agent soul
Quality check:
Who I Am section ✓ present
Worldview section ✓ present
Opinions section ✓ present
Vocabulary section ✓ present
Boundaries section ✗ missing — run /soul-enhance to add
Size ✓ ~2,847 tokens (under 5K limit)
Summary: 1 enabled, 1 disabled, 6 not found
To enable: /soul-enable
To disable: /soul-disable
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.
- 7d ago First seen · 177 lines · 17 tokens per session scan A a24b58f0758f
soul-status is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 1,436 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
goal-writer
Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user says "draft a goal", "write a goal+rider"…
horizon
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
check-in
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
hyperplan
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.