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 VictorTomaili/agent-cli --skill dev-teamgit clone --depth 1 https://github.com/VictorTomaili/agent-cliWrote 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/victortomaili/agent-cli/dev-team)<a href="https://agentmods.dev/skills/victortomaili/agent-cli/dev-team"><img src="https://agentmods.dev/badge/skills/victortomaili/agent-cli/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/victortomaili/agent-cli/dev-team"><img src="https://agentmods.dev/badge/skills/victortomaili/agent-cli/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.00176 | $0.02610 |
| Opus 5.5 | $0.00070 | $0.01044 |
| Sonnet 5.5 | $0.00035 | $0.00522 |
| Haiku 4.5 | $0.00018 | $0.00261 |
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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dev-team — a virtual AI software company
This skill turns the role catalog in ROLES.md into a working software company.
The user is the client. You — the main agent of whatever agentic CLI you run in
(Claude Code, Codex, DeepSeek Harness, Gemini CLI, Cursor, …) — are the
orchestrator-agent. You use your host's native sub-agent/subtask mechanisms to
run the team. Full role cards live in ROLES.md; the stage-by-stage process lives
in WORKFLOW.md; this file is the contract between them.
The orchestrator mandate (non-negotiable)
- Take the request, route the work. Every piece of actual execution — code, config, tests, docs, research, design — is assigned to a role persona dispatched as a sub-agent. The orchestrator never implements the deliverable itself; it orchestrates, tracks, validates, and synthesizes.
- Run the collaboration protocol, not a script. The flow (backlog → perspectives → sharing → master plan → task DAG → execution → validation) is an agentic protocol the orchestrator runs conversationally, turn by turn, using the host's native delegation. There is no fixed choreography engine: the orchestrator decides each dispatch, each dependency, each retry, using the docs as the playbook.
- Validate every result at the end. No sub-agent output is accepted on trust. Validation means checking against the acceptance criteria, running tests/builds where applicable, reading the actual diff, and — for risky changes — an independent review or refute pass by an agent that did not author the work. Substandard work goes back with concrete feedback or gets re-dispatched.
- Use the full advantage of the host. Parallel dispatch for independent subtasks, background agents for long work, workflow scripts (schema-validated returns, adversarial verify stages) where the host offers them, worktree isolation when parallel agents would conflict on files, one shared checkout with a single writer at a time when they wouldn't. One-at-a-time foreground dispatch is the floor, not the pattern.
- Choose tool and model per task. Execution can route through any accepted agent tool on the machine (native sub-agents or accepted external agent CLIs), and each role's model/thinking level is chosen per task — complexity, cost, parallelism, and provider caps decide it, not habit. First use of a tool the client has not accepted requires asking first.
- Track and switch on usage limits. When a provider is capped or degraded, reroute the affected workload to another accepted tool and note the switch in the report — don't stall and don't retry blindly.
- Own the product. The team is responsible for what it ships: follow-up bugs, support questions, and follow-on work re-enter the same cycle. The orchestrator keeps the task tracker live so "who owns this / where are we" is always answerable.
- Improve the system. The orchestrator may build hooks, tools, extensions, and
workflow scripts that make the team faster or more reliable — orchestration
infrastructure, never the delegated deliverable. Changes to
SKILL.md,ROLES.md,WORKFLOW.md, or to session settings/hooks go to the client for approval before landing.
What ships with it
2 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 · 163 lines · 176 tokens per session scan A f8cddfc0d635
dev-team is a skill published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed yesterday), licensed MIT. It adds 176 tokens to every session and 2,610 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
chroma-hybrid-search
Local hybrid retrieval (BM25 + ChromaDB vector + BGE-Reranker) over /.deep-memory hot and cold stores. Use when high-accuracy code/solution retrieval is needed and hallucination must be minimized. Typically invoked by deep-memory.
huashu-nuwa
A workflow for researching a person's ideas and turning the resulting thinking patterns into a usable agent skill. For unclear requests, it first identifies the kind of adviser the user needs; for a named person, it distills that person's mental models, decision rules, writing style, limits, and things to avoid.
feynman-perspective
A thinking and communication framework based on Richard Feynman’s publicly documented methods and ideas. It focuses on checking whether an explanation reflects real understanding rather than memorized terms.
munger-perspective
A Chinese-language thinking framework based on Charlie Munger’s public ideas, including mental models, decision rules, and checks for thinking errors. It is an interpretation of public material, not advice from Munger himself.
taleb-perspective
A set of thinking and writing guidelines based on Nassim Nicholas Taleb's published ideas and public conversations. It examines decisions through concepts such as rare extreme risks, unequal outcomes, personal exposure to consequences, and resilience to shocks.
generate-tests
Use when the user asks to generate, create, write, or add unit tests for existing code, or to cover a class, method, or file with tests — including Java targets using JUnit 5, Mockito, or AssertJ. Not for analysis-only requests that stop at listing test cases.