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 pwdev-solucoes/pwdev-claude-marketplace --skill feat-initgit clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplaceWrote 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/pwdev-solucoes/pwdev-claude-marketplace/feat-init)<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-init"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-init/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/pwdev-solucoes/pwdev-claude-marketplace/feat-init"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/feat-init.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.00090 | $0.00796 |
| Opus 5.5 | $0.00036 | $0.00318 |
| Sonnet 5.5 | $0.00018 | $0.00159 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
feat-init 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 27d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize pwdev-feat
.planning/config.json is shared with other PWDEV plugins: always merge, never overwrite.
Procedure
- Language (mandatory here) — show the current
langif set and ask to keep or change; otherwise askpt-BRoren(references/language.md). Merge"lang". - Model profile — show the current
model_profileif set and ask to keep; otherwise present the selection prompt fromreferences/model-profiles.md. Optionally ask for overrides, saved ONLY under the namespaced keysfeat-executor/feat-advisorinmodel_overrides. - Workspace — if
.planning/feat/features/exists, say it is already initialized and stop unless the human asks to re-run the configuration. Otherwise create.planning/feat/features/and.planning/feat/context/. - Audit trail (opt-in, default off) — show the current
auditvalue or ask: "Enable the local SQLite audit trail? (records commands, dispatches, decisions and planning artifacts; the .db is never versioned)". Merge"audit": true|false. When enabled, runpython3 "<plugin-root>/scripts/audit.py" init(creates the shared schema and.planning/.gitignore; the project's own.gitignoreis never touched) and log each changed field:sh "<plugin-root>/scripts/audit-log.sh" config <field> "<old>" "<new>" init. Mechanical recording (session, subagent duration, artifact writes) happens through hooks on Claude Code only; on Codex, Hermes and OpenCode the skills log their milestones explicitly. - Detect (read-only) the stack in one pass:
python3 "<plugin-root>/scripts/feat_map.py" --repo-root .— show languages, frameworks, test frameworks and whether a project instructions file exists. Do not publish anything here. - Summary:
✅ pwdev-feat initialized — lang {lang} · profile {profile} · audit {on|off} · runtime {runtime} 📁 .planning/feat/features/{slug}/ plan.md · progress.md · plan.done.md · review.md / test-audit.md 📦 Detected: {stack} 🚀 Next: feat-map (recommended for existing projects) → feat-setup → feat-feature "description" Quick task without a plan: feat-quick "description"
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.
- 27d ago First seen · 53 lines · 90 tokens per session scan A b6ae536c8b62
feat-init is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 90 tokens to every session and 796 once invoked, about $0.0004 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-09-28.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.