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/spumer/i-m-senior-developer/dpf-applynpx skills add spumer/i-m-senior-developer --skill dpf-applygit clone --depth 1 https://github.com/spumer/i-m-senior-developerWrote 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/spumer/i-m-senior-developer/dpf-apply)<a href="https://agentmods.dev/skills/spumer/i-m-senior-developer/dpf-apply"><img src="https://agentmods.dev/badge/skills/spumer/i-m-senior-developer/dpf-apply.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.00181 | $0.02553 |
| Opus 5 | $0.00090 | $0.01277 |
| Sonnet 5 | $0.00036 | $0.00511 |
| Haiku 4.5 | $0.00018 | $0.00255 |
Grade A, and why
dpf-apply 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 today.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dpf-apply — резолвер и исполнитель пакетов компетенций
Скилл сам не содержит ни одной компетенции. Он резолвит id пакета (DPF-… / LPF-…) до файла на диске и запускает нужный режим использования — как знание (ground) или как процедуру с типизированным выходом (apply). Каждое использование — пара «пакет × объявленное применение» (E.4.DPF.DA: declaredUse, nonUseBoundary, intendedReaderOrOperator, reopenCondition); скилл не даёт применить пакет «просто так», без этой пары.
packageKind включает local-practice-framework и skill-pack — сам dpf-apply при установке из плагина является пакетом kind=skill-pack (см. README, сценарий 3).
Резолюция
python3 <каталог этого скилла>/scripts/resolve.py <id> [--json]
python3 <каталог этого скилла>/scripts/resolve.py --list [--json]
python3 <каталог этого скилла>/scripts/resolve.py --sources [--json]
Каталог скилла — тот, из которого прочитан этот файл; при установке из плагина это plugins/fpf-integration/skills/dpf-apply.
Порядок уровней (первый выигрывает при затенении id):
- project —
$PWD/.claude/frameworks/<ID>/ - user —
~/.claude/frameworks/<ID>/ - plugin — непустые строки без комментариев сначала из
~/.claude/frameworks.paths, затем из~/.claude/frameworks.published
Повторные корни исключаются по каноническому пути; остаётся первое вхождение. frameworks.paths — человеческий список: резолвер читает его, но не записывает. --sources печатает по строке на каждый объявленный корень: уровень, происхождение (project, user, paths, published), путь и существование каталога; режим всегда завершается кодом 0.
Указатель frameworks.published называет корень целиком, а не отдельный допущенный пакет, поэтому пакет из такого корня проходит банковский допуск на самом обычном пути резолюции: без строки допуска E.4.DPF.DA в его DPF.md резолвер отказывает кодом 2 и называет причину, --list помечает строку как «без допуска», а подсказка такой пакет не предлагает. Корень, названный человеком в frameworks.paths, остаётся вне допуска — ответственность за него взял человек; уровни project и user не затронуты, там работа над черновиком без итогового вердикта разрешена намеренно. Поля published и admissible в выдаче --json показывают это состояние машинно.
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.
- today Changed · +5 lines 3d0ad1fa283d
- 4d ago First seen · 96 lines · 181 tokens per session scan A bae920c76d4b
dpf-apply is a skill published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 2d ago), licensed MIT. It adds 181 tokens to every session and 2,553 once invoked, about $0.0009 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…