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 JansenAnalytics/claudex --skill whoamigit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/whoami)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/whoami"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/whoami.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.00078 | $0.00637 |
| Opus 5 | $0.00039 | $0.00318 |
| Sonnet 5 | $0.00016 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
whoami 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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
whoami
Renders the auto-curated user profile — the structured memory/USER.md that the
memory-curate cron job (scripts/memory-curate-cron.sh, every 2 h) maintains and that
session-init.sh loads into every session.
This is the read-only review surface for the profile (Tier 2 item 4C). It does not edit anything — it shows the profile, how big it is against the ~500-token cap, and where it needs pruning.
Run it
bash "$CLAUDE_SKILLS_DIR/whoami/scripts/whoami.sh"
If $CLAUDE_SKILLS_DIR is unset, the script lives at ~/.claude-agent/.claude/skills/whoami/.
What it shows
- The full profile, rendered.
- Last updated timestamp and size / token estimate vs the 500-token cap.
- Per-section counts across the five schema sections:
stable_facts · preferences · working_patterns · recent_corrections · open_threads. - A prune nudge for the rolling sections (recent_corrections keeps newest 8, open_threads keeps newest 6).
The schema (maintained by memory-curate.cjs)
- stable_facts — identity, timezone, environment, tooling (rarely change)
- preferences — how the user likes work done
- working_patterns — recurring workflows, cadences
- recent_corrections — explicit corrections / things that superseded an old belief (newest first)
- open_threads — in-flight work to resume
How to prune
This skill is read-only. To prune, edit memory/USER.md by hand:
- fold a settled
recent_correctionsentry intopreferences/stable_factsand delete the correction, - remove
open_threadsthat are finished, - tighten any
stable_facts/preferencesthat have drifted.
The distiller never deletes core facts — only you do, here. It only trims the rolling sections to newest-N and enforces the token cap.
Rules
- Never edit the profile from this skill — it only reports.
- If the profile is over the token cap, surface that first and recommend a prune.
- CLAUDE.md is separate and hand-written —
whoamishows the learned profile, not the rules.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 60 lines · 78 tokens per session scan A 972501413b5c
whoami is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 637 once invoked, about $0.0004 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-03.
Other skills, from other repositories
antigravity-skill-orchestrator
A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.
forgetful-remember
Remember knowledge worth keeping — a decision made, a solution found, a preference stated, a pattern confirmed. Use when work surfaces something future sessions will need, or the user asks to remember something. Routes content to the right store (memory, document, code artifact, entity, procedure, file) and enforces…
a0-plugin-router
Main entry point for all Agent Zero plugin tasks. Routes to specialist skills for creating, reviewing, contributing, managing, or debugging plugins. Use when the user mentions plugins, asks how the plugin system works, wants to build/install/uninstall/publish/debug a plugin, or asks about the Plugin Hub.
continuous-learning
Use when a mistake, correction, or surprise taught the workspace something that must stick — a retro or postmortem, the same agent error corrected twice, a resolved bug's root cause, scattered notes-to-self — and route that lesson to the durable surface that fires next time. NOT a forward choice with alternatives…
capability-evolver
Self-evolution workflow for the agent. Before substantive work, recall past outcomes from evolution memory; while editing, detect improvement signals; at task end, record the outcome; when reusable, distill or search the EvoMap network for proven genes/capsules. Use when the user starts non-trivial work (a feature, a…
update-user-profile
Update user profile information when user shares preferences, habits, or work details. When you need to save user preferences, remember user's work domain, or provide personalized service.