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/setup)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/setup"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/setup/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/setup"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/setup.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.00174 | $0.12860 |
| Opus 5.5 | $0.00070 | $0.05144 |
| Sonnet 5.5 | $0.00035 | $0.02572 |
| Haiku 4.5 | $0.00017 | $0.01286 |
Grade C, and why
setup scanned grade C with 2 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 17d 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 for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| Linux (apt) | `sudo apt-get install -y jq` | Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -qF "$MARKER" .claude/CLAUDE.md 2>/dev/null && echo "concise-preference-already-covered" || echo "concise-preference-not-yet-covered" How it starts
The opening of the file, as written. The whole thing — 1,106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup
Role: orchestrator. See frontmatter description for scope; delegates all
stack detection and toolchain install/inventory to /dev-team:project-init,
which /setup never re-derives.
Orchestrator constraints
- Detect and scaffold; delegate generation, do not review code yourself.
- Install prerequisites and write config only where the user confirms.
- Do not overwrite existing project config without confirming.
- Be OS-aware; do not assume a package manager.
- Be concise. Report detected stack, installed prerequisites, and generated artifacts — no narration.
Parse Arguments
Arguments: $ARGUMENTS
--dry-run: Report what would be created/installed without writing any files or installing anything.--yes: Run unattended — auto-confirm every prompt with its safe default and pass--yesthrough when invoking/dev-team:project-init(Step 4). No step waits for input.--autocompact-pct N: writeN(integer 1-100) as the repo'sCLAUDE_AUTOCOMPACT_PCT_OVERRIDE(Step 9b) instead of the default40.--no-autocompact: skip Step 9b's settings write and silence the SessionStart nudge that recommends running/dev-team:setup.
--yes semantics (the unattended contract)
When --yes is set, take these actions without prompting. Affirmative —
auto-confirm and proceed:
- Per-language mutation tooling for the detected stack (Step 6). Already
non-interactive when the stack is definite;
--yesadditionally suppresses the ambiguous-stack fallback below. - Agent-template activation for the detected stack (Step 7).
- Project
CLAUDE.md(Step 8) and/pr(Step 10) generation when the file is absent; the downstream.gitignoreappend (Step 11). - Everything
/dev-team:project-initauto-confirms under its own--yes(its three-column plan, capability tools whose signal fired, and the keyless CodeGraph + Repowise pair — see that skill's Arguments section).
Conservative — never silently overwrite an existing file or mutate the repo in a surprising way; take the skip default and print a one-line note:
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.
- 17d ago Changed · +27 lines 069a2e9fa906
- 1mo ago Changed · +104 lines scan B → C eeb804230018
- 1mo ago First seen · 975 lines · 174 tokens per session scan B 256c66bd6da8
setup is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 174 tokens to every session and 12,860 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.