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 saemihemma/lead-producer-oss --skill team-dev-teamgit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/team-dev-team)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/team-dev-team"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-dev-team/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/saemihemma/lead-producer-oss/team-dev-team"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-dev-team.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.00033 | $0.00527 |
| Opus 5 | $0.00016 | $0.00264 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
team-dev-team 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 9d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Team
Purpose
Single technical verdict on whether implementation is structurally sound, maintainable, and sufficiently verified.
Composition
- role-software-architect: structure, boundaries, design fit
- role-principal-software-engineer: code quality, maintainability, tech debt
- role-qa-engineer: test coverage, regression risk, verification gaps
- Synthesis: conflict handling, acceptance
Use When
- Reviewing a pull request, module, or implementation slice
- Validating a refactor or design before merge
- Checking code quality and verification match intended architecture
Do NOT Use When
- Adversarial security review (use
team-red-team) - Product, UX, or economy analysis
- Reduction verification (use
team-blue-team)
Workflow
- Check what already exists before judging what should change.
- Review structure, code quality, and test posture together.
- Run specialist passes in parallel. QA pass includes AI test quality checks (redundancy, assertion strength, isolation) on any test suite under review.
- Merge findings: test gaps map to risky code, risky code maps to architecture.
- Call out what is out of scope and the top failure modes.
- Resolve conflicts, produce one technical verdict.
Default Output
DEV TEAM REVIEW
===============
Current State: relevant existing code paths, boundaries, reuse opportunities
Architecture: boundary/design concerns
Code Quality: maintainability findings, debt/complexity risks
Verification: test gaps, regression risks
Failure Modes: top breakages to watch, what is not in scope
Recommendation: merge / rework / escalate, highest-priority fixes
Success Criteria
- Architecture, code quality, and verification connected rather than siloed.
- Output states what blocks acceptance vs what is advisory.
Conflict Resolution
- Architect owns structural decisions. Principal Engineer owns code-quality assessment. QA owns verification gaps.
- When architecture and code-quality findings conflict, resolve by asking: "What serves the next engineer better?"
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.
- 9d ago First seen · 60 lines · 33 tokens per session scan A 4627862de3e8
team-dev-team is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 527 once invoked, about $0.0002 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
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
semgrep-rule-variant-creator
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.