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.
/plugin marketplace add spumer/i-m-senior-developernpx agentmods add plugins/spumer/i-m-senior-developer/fpf-integrationgit clone --depth 1 https://github.com/spumer/i-m-senior-developerGrade A, and why
fpf-integration 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.
What it actually says
{
"name": "fpf-integration",
"version": "0.6.2",
"description": "Экосистема First Principles Framework: интеграция FPF в multi-agent проекты (аудит решений, DRR, навигация по спеке — через FPF-справочник MCP, если подключён, иначе локальная копия; без источника скилл блокируется, а не деградирует), авторинг сводов принципов dpf-authoring (6-фазный конвейер со встроенными пакетами ролей), резолвер-исполнитель пакетов компетенций dpf-apply (ground/apply, гейт свежести, журнал worked-evidence) и установщик ритуала end-session-setup (шаг worked-evidence в закрытие сессии). Агент dpf-gate — гейт перед работой со сводом: проверяет допуск, называет режим и возвращает план на подтверждение; инструментов записи у него нет, править своды он не может.",
"author": {
"name": "spumer"
},
"keywords": ["fpf", "first-principles", "dpf", "dpf-apply", "framework-apply", "dpf-authoring", "evidence", "decision-quality"]
}
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 · 10 lines scan A 95680e3d0f12
fpf-integration is a plugin published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.