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 timurgaleev/memex --skill soul-auditgit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/soul-audit)<a href="https://agentmods.dev/skills/timurgaleev/memex/soul-audit"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/soul-audit/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/timurgaleev/memex/soul-audit"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/soul-audit.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01043 |
| Opus 5 | $0.00027 | $0.00522 |
| Sonnet 5 | $0.00011 | $0.00209 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
soul-audit 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 9d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Soul Audit — Agent Identity Builder
Generate the agent's identity and operational configuration through an interactive
interview. Each phase produces a brain page. Any phase can be re-run independently
to update. The get_brain_identity tool serves these pages back to any connected
agent, so what you write here shapes every future session.
IMPORTANT: This skill generates content from the OPERATOR'S OWN ANSWERS. It NEVER ships pre-filled content. The minimal scaffolds in Default Mode are skeletons, not defaults.
Contract
This skill guarantees:
identity/soulgenerated from the operator's description of agent identity, vibe, missionidentity/usergenerated from the operator's self-description (role, projects, key people)identity/access-policygenerated with an explicit access postureidentity/heartbeatgenerated with the operational cadence the operator chooses- Each phase is independent and re-runnable
- Default mode (skip soul-audit): writes minimal scaffold pages via
page_put
Phases
Phase 1: Identity Interview
Ask: "What is this agent to you? Research partner? Executive assistant? Thinking partner? All of the above?"
Generate: identity/soul identity section (page_put).
Phase 2: Vibe Calibration
Show 3-4 communication style examples:
- Formal: "I've prepared a comprehensive analysis of the situation..."
- Direct: "Here's what's happening. Three things matter."
- Technical: "The root cause is in the connection pooling. Here's the fix."
- Casual: "Yeah so basically the thing is broken because X. Easy fix."
Ask which feels right. Generate:
identity/soulvibe + communication style sections.
Phase 3: Mission Mapping
Ask: "What are your top 3-5 goals? What are you trying to accomplish?"
Generate: identity/soul mission + operating principles sections.
Phase 4: Operator Profile
Ask: "Tell me about yourself. What do you do? What are you working on? Who are the key people in your world?"
Generate: identity/user with role, projects, key people, communication preferences.
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.
- 9d ago First seen · 106 lines · 54 tokens per session scan A 962c924a9b89
soul-audit is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,043 once invoked, about $0.0003 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
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…