Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/me/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/me)<a href="https://agentmods.dev/skills/egregore-labs/egregore/me"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/me/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/egregore-labs/egregore/me"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/me.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.00049 | $0.00821 |
| Opus 5 | $0.00024 | $0.00411 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
me 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 10d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/me — View or reconcile your identity
Show the current member identity or change how the member wants to be called. All writes go through one portable identity spine shared by Claude Code, Codex, and Pi.
When to invoke
- "who am I", "my profile", "my name", "what's my name"
- "call me Oz", "I go by Cem", "change my name to X"
- "use [email protected] for me", "add/change my email"
- User runs
/meor/me <name>
Identity contract
bin/person.sh is the only writer for person identity. It reconciles:
.egregore-state.json— local runtime identity;memory/people/{github_username}.md— durable organizational profile;- Supabase
users+memberships— platform identity and per-org display name; - Neo4j
Person— knowledge-graph identity and relationships.
The durable identity is GitHub's numeric user id (person_id=github:<id>)
when available. GitHub login, preferred/display name, historical names, and
emails are aliases/addresses of that identity. A login rename or preferred-name
change must update the same person, not create another member.
External people introduced by $ingest remain source-scoped external
identities and are never promoted into members by this workflow.
No arguments
Run:
bash bin/person.sh show
Display the useful fields only:
Name: {display_name}
GitHub: {github_username}
Email: {email or "not shared"}
Aliases: {github_aliases + previous_names, if any}
Never expose internal platform ids unless the user asks for diagnostics.
With a name
Run:
bash bin/person.sh set-name "$ARGUMENTS"
The command validates the name, preserves the old display name as an alias, updates the canonical markdown profile, reconciles simple duplicate/alias profiles, syncs Supabase, updates the graph, and moves known relationships from duplicate Person nodes onto the canonical member.
Report:
synced→You're now known as **{name}** everywhere in this Egregore.synced-local→You're now known as **{name}** in this Egregore.partial→ the local state and markdown are durable; say which projection (supabaseorgraph) is pending and that a laterbin/person.sh syncretries it.
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.
- 10d ago First seen · 109 lines · 49 tokens per session scan A 56da66320d82
me is a skill published in the GitHub repository egregore-labs/egregore (282 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 821 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-30.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
xiaohongshu-image-creator
An image-making assistant for Xiaohongshu, a Chinese social platform for lifestyle, product, and educational posts. It creates vertical covers and supporting images matched to the post’s topic, audience, and visual style.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…