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 ytvee-dev/webdev-agent-kit --skill project-context-adaptergit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWrote 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/ytvee-dev/webdev-agent-kit/project-context-adapter)<a href="https://agentmods.dev/skills/ytvee-dev/webdev-agent-kit/project-context-adapter"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/project-context-adapter/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/ytvee-dev/webdev-agent-kit/project-context-adapter"><img src="https://agentmods.dev/badge/skills/ytvee-dev/webdev-agent-kit/project-context-adapter.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.00031 | $0.01656 |
| Opus 5.5 | $0.00012 | $0.00662 |
| Sonnet 5.5 | $0.00006 | $0.00331 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
project-context-adapter 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 12d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context Adapter
Purpose
Refresh factual host-project context in project/** so reusable skills can
implement screenshot-derived specs without scanning the whole repository.
When To Use
- Project structure, routes, entrypoints, styling systems, assets, or verification commands changed.
- A new frontend stack fact was discovered during implementation.
- Current skill capability declarations, available providers, or official documentation choices changed.
- Design-reference boundaries, approved patterns, or anti-patterns changed.
- Path indexes no longer match actual source files.
When Not To Use
- Upgrading the installed Kit version: use
webdev-kit-updater; refresh only facts its changed contracts invalidate. - First-time full onboarding in Plan Mode. Use
project-onboarding-adapter. - Reusable skill authoring. Use
agent-rules-skill-author. - Screenshot spec writing or implementation unless project facts changed.
Required Context
- Read
AGENTS.mdwhen shipped, or the native plugin's generated runtime prelude. Resolve local overlays under host.agents/project/, not inside a shared plugin installation. - Confirm the classified task is
project-context-refreshor a project context cache update required by another task. - Read
common/documentation-maintenance.md. - Read existing
project/**overlays. - Inspect relevant manifests, configs, entrypoints, routes, components,
styles, assets,
tool-capabilities-manifest.json, and verification scripts. - Read
references/extraction-checklist.md. - Read
references/sync-procedure.md. - Read
common/project-fact-provenance-rules.md; preserve unrefreshed dates and mark unexecuted checksnot-run.
Read targeted README sections only when the refresh concerns project intent, setup guidance, or documentation drift. Use common/readme-policy.md and confirm cached technical facts through higher evidence.
Tool Contract
- Use Project Context MCP when available.
- Use filesystem reads and targeted search when Project Context MCP is unavailable.
- Use
context7and MDN only when refreshing official documentation choices or stack-specific pattern notes that depend on current external docs. - Activate
openai_platform_docsonly when refreshed project facts depend on current OpenAI or Codex behavior. - Do not use Figma MCP.
- Edit only
project/**unless the user also requests bundle skill or policy changes.
What ships with it
3 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.
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.
- 12d ago Changed · +3 lines b1fe9c6bda3e
- 1mo ago Changed · +22 lines · -16 tokens per session 8b23a0fd2409
- 1mo ago First seen · 150 lines · 47 tokens per session scan A f9293b7d4d9b
project-context-adapter is a skill published in the GitHub repository ytvee-dev/webdev-agent-kit (7 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,656 once invoked, about $0.0001 per session on Opus 5.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
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
playwright-frontend
For frontend engineers authoring UI — how to make components reliably locatable by tests and AI agents. Covers the official Playwright locator priority, semantic/accessible markup first, and how to add valid, unique, stable data-testid attributes (naming convention, uniqueness in lists, stability rules) for React…
playwright-qa
QA engineering workflows on top of Playwright. Use when a QA engineer asks to design test cases from a ticket, PRD or acceptance criteria, decide what to automate, write a bug report from a failing test or trace, convert manual test cases (TestRail, Xray, CSV) into Playwright specs with case-ID traceability, or review…
agent-wiki
Incremental LLM-friendly wiki generator for Obsidian note vaults. Use when: (1) Building wiki from notes, (2) Ingesting notes to wiki, (3) Obsidian LLM wiki, (4) Incremental knowledge base management. Triggers: 'build wiki from notes', 'ingest notes to wiki', 'Obsidian LLM wiki', 'incremental knowledge base'.
context-optimizer
A context-management assistant for long conversations with AI agents. It helps organize the information an agent needs when conversations become large or contain conflicting details.