Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/project-init)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/project-init"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/project-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/bdfinst/agentic-dev-team/project-init"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/project-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.00309 | $0.16002 |
| Opus 5.5 | $0.00124 | $0.06401 |
| Sonnet 5.5 | $0.00062 | $0.03200 |
| Haiku 4.5 | $0.00031 | $0.01600 |
Grade A, and why
project-init scanned grade A with 1 finding 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 1mo 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.
Asks the agent to reveal its instructionslowSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
run — it is not a "print instructions and leave it to the user" step (issues Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 1,188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Initializer
One command to get a repository ready for the dev-team toolchain, whatever the stack. Detect the project's language(s), inventory the static-analysis tools already present, confirm a three-column plan, then install only the missing tools — lane tools and Playwright always repo-level, never user-level or global. It then installs the detection-gated capability tools other skills depend on (semgrep, Playwright, adr, gh, docker scanners — see Step 4b), which are user/system-level CLIs by nature.
Supported stacks: JS/TS, Python, C#, Java — the four lanes
registered in
${CLAUDE_PLUGIN_ROOT}/skills/static-analysis-integration/references/tool-configs.md
§ Build-time lanes. Tool facts (choice, versions, install mechanism) follow
that registry; provider-binding semantics (capability slots, ordered
provider lists, bind-don't-replace, the qualification contract) follow
${CLAUDE_PLUGIN_ROOT}/skills/build/references/static-self-heal.md. The
manual commands stay documented in
${CLAUDE_PLUGIN_ROOT}/skills/static-analysis-integration/references/language-setup.md;
this skill automates them.
Arguments
Arguments: $ARGUMENTS
--yes: Run unattended — auto-confirm each gate below with its safe default and never wait for input./setup --yespasses this through.--force: Bypass Step 0's idempotency short-circuit and force the full Step 1-6 sequence even when.claude/init-state.jsonrecords a matchinglast_run(#1778). Independent of--yes— combine them to force a full unattended re-check.
--yes semantics
Affirmative (auto-confirm, no prompt):
- Step 3 three-column plan — proceed: install the "missing and will add" column's defaults, repo-level. Existing configs are still never overwritten (that is already the plan's contract, not a prompt).
- Step 4b capability tools — install every tool whose detection signal fired and that is still missing. Tools whose signal did not fire are still not installed.
- Step 4c CodeGraph — install if missing (its recommended default is already yes, as part of the interactive keyless-pair prompt — see Step 4c). CodeGraph never writes to the repo, so it stays in this bucket. Repowise, offered alongside it in the same interactive prompt, does not stay here — see the Conservative bucket below (#1690).
What ships with it
4 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.
- 1mo ago First seen · 1,188 lines · 309 tokens per session scan A 9e00d60ec3d8
project-init is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 309 tokens to every session and 16,002 once invoked, about $0.0012 per session on Opus 5.5. A static security scan graded it A with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.