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 cpliakas/claude-code-engineering-leaders --skill re-onboardgit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/re-onboard)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/re-onboard"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/re-onboard/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/cpliakas/claude-code-engineering-leaders/re-onboard"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/re-onboard.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.00117 | $0.03396 |
| Opus 5 | $0.00059 | $0.01698 |
| Sonnet 5 | $0.00023 | $0.00679 |
| Haiku 4.5 | $0.00012 | $0.00340 |
Grade A, and why
re-onboard 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 8d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Re-onboard
Audit onboarded agent project memory for drift against live project signals. Produces a per-agent diff report grouped into drifted, unchanged-notable, and new items. Phrases every finding as a question the user confirms or dismisses. Writes updates to memory only after explicit user confirmation.
Run this skill after a structural project change (renamed directories, new CI provider, migrated issue tracker, specialist agents added or removed), on a periodic cadence, or when an agent gives advice that feels out of date.
If invoked without an argument, audits every onboarded agent and the shared
Layer 1 context. If invoked with an agent name (for example, /re-onboard tech-lead), restricts the audit to that agent's memory directory.
Process
1. Discover Onboarded Agents
Determine the scope of the audit.
Full run (no argument): Glob for all agent memory directories under the project root:
.claude/agent-memory/engineering-leaders-*/MEMORY.md
Exclude .claude/agent-memory/engineering-leaders/PROJECT.md. That is the
Layer 1 shared context, not an agent memory directory. Treat any directory
matching engineering-leaders-<agent-name>/ that contains a readable
MEMORY.md as one onboarded agent. Collect the agent names from the directory
suffix (for example, engineering-leaders-tech-lead yields tech-lead).
Also check for the Layer 1 shared context at:
.claude/agent-memory/engineering-leaders/PROJECT.md
If found, include it in the audit as the shared context layer (handled in Step 3).
If no agent memory directories exist and no PROJECT.md exists, report:
No onboarded agents found. Run /onboard or /onboard-<agent-name> to create
project memory for this project.
And exit without further checks.
Scoped run (argument provided): Check for a memory directory at:
.claude/agent-memory/engineering-leaders-<argument>/MEMORY.md
If the directory does not exist or contains no readable MEMORY.md, report:
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.
- 8d ago First seen · 357 lines · 117 tokens per session scan A 81b7fac595e0
re-onboard is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 17d ago), licensed MIT. It adds 117 tokens to every session and 3,396 once invoked, about $0.0006 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.