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/ytvee-dev/webdev-agent-kit/project-context-adapternpx skills add ytvee-dev/webdev-agent-kit --skill project-context-adaptergit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWhat 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.00047 | $0.01337 |
| Opus 5 | $0.00023 | $0.00668 |
| Sonnet 5 | $0.00009 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00134 |
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 2d 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 — 150 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
- 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.md. - 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 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.
- 2d 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 (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,337 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-31.
Other skills, from other repositories
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-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…
shipping-reproducible-results
Package completed data analysis and ML work so an independent recipient can reproduce the claimed results, verify artifact lineage, and operate the handoff within its stated scope. Use when finalizing a project, study, model package, or review bundle; not for deploying to a live system.
actions-reusable-workflows
Wire a repository to the bitwise-media-group/github-workflows reusable workflows — thin, SHA-pinned caller workflows for CI, security (CodeQL) scanning, release (release-please/GoReleaser/Zensical docs), the signature-preserving fast-forward /merge + merge-review-ack + merge-notice flows, and add-to-project — plus the…
go-style
Modern Go code style for stdlib-first programs — error wrapping with %w, sentinel errors, structured logging with log/slog, context threading, consumer-defined interfaces, nil-safe constructors, net/http servers with method-pattern routing, flag/env configuration for services, and cobra commands with viper…
workflow-skill-evals
Write the evolve evaluation suite for an agent skill: its triggers (triggers.json — Tier 1 activation tests) and behavioral evals (evals.json — Tier 2 task tests), under evals/ /. Use when asked to generate, write, author, scaffold, or balance an eval suite, evals, or triggers for a skill; to create or edit a…