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 agentmods add skills/linkpranay-ai/context-engineering-protocol/vendored-skillnpx skills add linkpranay-ai/context-engineering-protocol --skill vendored-skillgit 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/vendored-skill)<a href="https://agentmods.dev/skills/linkpranay-ai/context-engineering-protocol/vendored-skill"><img src="https://agentmods.dev/badge/skills/linkpranay-ai/context-engineering-protocol/vendored-skill.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 | $0.00000 | $0.04644 |
| Opus 5 | $0.00000 | $0.02322 |
| Sonnet 5 | $0.00000 | $0.00929 |
| Haiku 4.5 | $0.00000 | $0.00464 |
Grade A, and why
vendored-skill 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 5d 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: spw-write-user-story description: Write user stories (functional, NFR, Enabler) for a feature from an approved ult-context-generate context package — actor-driven coverage, constraint routing, Enabler/Requirement-Note shaping. namespace: spw version: 0.1.0 origin: ground-up author: Pranay Mishra maintainer: Pranay Mishra adapted_from: ~ upstream_version: ~ released: 2026-06-30 tags: [developer, workflow, user-stories, requirements, actors, backlog, pilot] bundle: developer tier: act
spw-write-user-story
Status: piloting. The actor-identification pass (Step 2.5), the constraint routing table (Step 3b — Enabler stories vs. Requirement Notes vs. Sequencing Notes), and the coverage gates (Step 4 — actor coverage, NFR threshold, Requirement Note coverage, Enabler cross-reference) were validated end-to-end on a real RBAC guest-role feature, including the full Enabler/Requirement-Note backlog shaping for Jira-ready output, before this migration. This skill always runs against an approved
ult-context-generatecontext package (also piloting,utilitiesbundle) — install both bundles together. Report findings (works well / doesn't / surprises) back to its maintainers so this can graduate out of pilot status or be reworked.
Writes user stories for a given feature. Checks for an approved context package first;
if not found, invokes ult-context-generate before generating stories.
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.
- 5d ago First seen · 400 lines · 0 tokens per session scan A ce18de173626
vendored-skill is a skill published in the GitHub repository linkpranay-ai/context-engineering-protocol (8 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,644 tokens. 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
graft
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
bcc-plan-spar
BCC align+lock+review PLAN.md for one slice (no product code). Slash: /bcc-plan-spar · chat: bcc:plan-spar · "lock PLAN" · spar the plan. Args: rounds=N (auto-review cap), review=self|subagent|cli|auto|off. Grill until clear enough (no default Q&A quota). Hand off to bcc-clean-cut after human APPROVE.
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
bcc-breaking-coding-chaos
BCC main skill: dual-loop coding workflow (throughline → plan-spar → clean-cut) or quick status+next. Slash: /bcc-breaking-coding-chaos · chat: bcc:breaking-coding-chaos · "run BCC" · "BCC status" · "what next BCC". Needs a real idea (1:1 implement). Args: goal text, or status. May pass plan-spar review budget as…
bcc-clean-cut
BCC minimal implement from locked PLAN.md (ponytail ladder + verify). Slash: /bcc-clean-cut · chat: bcc:clean-cut · "implement PLAN" after human APPROVE. Not for plan grill (use bcc-plan-spar).