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 linkpranay-ai/context-engineering-protocol --skill ult-onboarding-indexgit clone --depth 1 https://github.com/linkpranay-ai/context-engineering-protocolWrote 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/linkpranay-ai/context-engineering-protocol/ult-onboarding-index)<a href="https://agentmods.dev/skills/linkpranay-ai/context-engineering-protocol/ult-onboarding-index"><img src="https://agentmods.dev/badge/skills/linkpranay-ai/context-engineering-protocol/ult-onboarding-index/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/linkpranay-ai/context-engineering-protocol/ult-onboarding-index"><img src="https://agentmods.dev/badge/skills/linkpranay-ai/context-engineering-protocol/ult-onboarding-index.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 122 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00210 | $0.02117 |
| Opus 5 | $0.00105 | $0.01059 |
| Sonnet 5 | $0.00042 | $0.00423 |
| Haiku 4.5 | $0.00021 | $0.00212 |
Grade A, and why
onboarding-index 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ult-onboarding-index
Overview
ult-repo-layout resolves where CEP content lives. ult-autoscaffold-content
and compiling-project-guidelines make sure real content exists at those
resolved paths. Neither of them assembles a single entry point into all of
it, and neither speaks the native onboarding dialect of each coding tool
(Copilot, Claude Code, Cursor, Codex). ult-autoscaffold-content/SKILL.md
names this gap explicitly, in its "What this skill deliberately does not do"
section:
Does not author Copilot/Claude/Cursor/Codex-specific instruction files or a root multi-tool onboarding index. That's a distinct, deferred concern — this skill's own output is tool-agnostic CEP content, consumed the same way regardless of which agent reads it.
This skill is that concern. It discovers what CEP-managed content already
exists in the target repo, then writes one canonical root AGENTS.md
plus thin per-tool pointer stubs that link into it — so a first-time user
of any of the four tools finds the same onboarding trail regardless of
which one they open first.
This is not this OSS repo's own root AGENTS.md. This repo's
AGENTS.md is generated by catalog/export_adapters.py's
render_agents_md() — a table of this library's own skill catalog. This
skill never touches that file. It runs inside a separate target repo
that has installed and is using CEP, and writes an AGENTS.md there
describing that repo's CEP content — a different document, in a
different repo, produced by a different mechanism. If you are looking at
this skill from inside context-engineering-protocol itself, it does
nothing here; it only acts on the repo it's invoked against.
Codex gets no separate pointer file. Root AGENTS.md is already
Codex's native onboarding format (this repo's own README.md documents
Codex Desktop reading it unprompted). Writing a Codex-specific stub file
would be redundant machinery with no consumer, so the per-tool pointer set
below covers three tools, not four.
What ships with it
8 files 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.
- references/marked-block-write-protocol.md 3.2 KB
- references/slot-discovery.md 4.2 KB
- scripts/onboarding_index.py 12 KB runs code
- scripts/tests/test_onboarding_index.py 8.7 KB runs code
- templates/agents-md-block-template.md 2.5 KB
- templates/claude-md-block-template.md 646 B
- templates/copilot-instructions-block-template.md 507 B
- templates/cursor-onboarding-mdc-template.md 685 B
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 · 169 lines · 210 tokens per session scan A 2728c1c60b1e
onboarding-index is a skill published in the GitHub repository linkpranay-ai/context-engineering-protocol (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 210 tokens to every session and 2,117 once invoked, about $0.0011 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
SDK Quickstart Writer
Generates a concise, copy-paste-ready quickstart guide for any SDK or library.
explain-codebase
Drop into any repo and generate a structured architecture overview. Maps the codebase, identifies entry points, frameworks, and dependencies — then produces a "start here" guide for new contributors.
First-Time User Tester
Validate the first-time user experience including onboarding flows, empty states, tutorial completion, progressive disclosure, and initial setup wizards.
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.
developer-marketing-playbook
Complete developer marketing playbook covering DevRel programs, documentation as marketing, API developer experience, community building, and hackathon strategy. For dev-tool founders who need to reach engineers. Follow @WeiYipei on X.
docmancer
Work from the same local memory as every other coding agent on this machine. Recall prior decisions, preferences, instructions, and project conventions that Claude Code, Codex, Cursor, and other agents wrote here, with cited sources, fully local. Also searches a separate local technical-documentation index.