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 gongyijie85/dsh-ecc --skill dev-teamgit clone --depth 1 https://github.com/gongyijie85/dsh-eccWrote 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/gongyijie85/dsh-ecc/dev-team)<a href="https://agentmods.dev/skills/gongyijie85/dsh-ecc/dev-team"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/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/gongyijie85/dsh-ecc/dev-team"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/dev-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 49 Skill grants unrestricted tool access without appropriate constraints. An agent with unfettered tool access can perform arbitrary actions including file modification, network requests, and code execution.Fix: Restrict tool access to only the tools required for the skill's stated purpose. Use an explicit allowlist rather than granting blanket access.
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.00060 | $0.01876 |
| Opus 5.5 | $0.00024 | $0.00750 |
| Sonnet 5.5 | $0.00012 | $0.00375 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
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 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.
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.
This is a copy
100% identical to dev-team — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Team
Run a multi-persona session where PM, Architect, Developer, and QA each respond from their own perspective in a single turn.
This is the preset four-lens review for collaborative design and planning. It is not
adversarial challenge (council), and it is not a free-form team composer
(team-builder selects arbitrary agents; dev-team always runs the same four roles).
When to Activate
The user provides a topic — a feature description, proposal, story, or question. The skill runs all four personas in parallel as independent subagents, then presents their responses together.
Use when:
- Designing a new feature and wanting PM, Architect, Dev, and QA concerns surfaced at once
- Reviewing a proposal before committing to implementation
- Onboarding an initiative and wanting each role to define their first concerns
- User says "what would the team think about this", "give me all perspectives", or "run this by the team"
- Starting a story and wanting role-specific input before writing a single line of code
When NOT to Use
| Condition | Use Instead |
|---|---|
| Ambiguous go/no-go decision with real tradeoffs | council |
| You want to hand-pick which agents participate | team-builder |
| Single-role deep-dive (e.g. architecture only) | the architect agent |
| Code review | the code-reviewer agent or /code-review |
| Structured adversarial challenge | santa-method |
Personas
| Role | Name | Lens |
|---|---|---|
| Product Manager | PM | user value, scope, prioritization, definition of done |
| Architect | Arch | system design, scalability, technical risk, integration points |
| Developer | Dev | implementation complexity, effort, edge cases, technical debt |
| QA Engineer | QA | testability, acceptance criteria, failure modes, regression risk |
All personas are analysis-only: they read the prompt they are given and answer from their role's perspective. They must not edit files, run state-changing commands, or use any tool that modifies the repository or external systems.
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 · 204 lines · 60 tokens per session scan A 727b093c8f82
dev-team is a skill published in the GitHub repository gongyijie85/dsh-ecc (9 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 1,876 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dev-team, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
manage-taskboard
Manage work in the native DeepSeek Harness Taskboard with exact task ids and optimistic versions. Use when an Agent must inspect project work, claim an eligible todo, record progress or blockers, verify an implementation, submit it for human review, or release its own claim; also use when a human asks how to accept…
wayfinder-zh
A planning workflow for turning a large, unclear effort into a map of decision tickets. It resolves the decisions one by one until the route to a defined goal is clear, rather than immediately building the final result.
product-prd
A Chinese-language product-definition and requirements workflow that turns an approved idea into a product definition and a PRD, a detailed product requirements document.
iteration
A product maintenance stage that turns user feedback into a prioritised feedback list, roadmap, and next-version plan.
ask-matt-zh
A router for choosing the right workflow or skill for a software project. It describes paths from an idea to shipped code, including research, prototypes, specifications, tickets, and implementation.
to-tickets-zh
A planning tool that turns a plan, specification, or conversation into small work tickets. Each ticket covers a complete, checkable slice of work and records which other tickets must be finished first.