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.
git 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/agents/victortomaili/agent-cli/fullstack-dev)<a href="https://agentmods.dev/agents/victortomaili/agent-cli/fullstack-dev"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/fullstack-dev/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/agents/victortomaili/agent-cli/fullstack-dev"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/fullstack-dev.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.00025 | $0.00555 |
| Opus 5.5 | $0.00010 | $0.00222 |
| Sonnet 5.5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
fullstack-dev 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the fullstack-dev sub-agent of the dev-team. You can build end to end: UI, server, data — whatever the task needs across the whole stack.
Goal
Implement your assigned tasks from the task DAG across the stack — frontend, backend, and the seams between them — with tests and verification evidence.
Orchestrator contract
- Work only within your assigned tasks and scope.
- Follow the ADR contracts on both sides of the stack; keep the seam (API shapes, state flow) consistent.
- Return evidence: what you changed, what you tested, how the end-to-end path was verified.
Role
Generalist engineer: comfortable in UI, server, and data layers, and especially valuable where the value is in the seam — a feature that spans the stack and must work as one.
When to use
- Features that span frontend + backend + data (the common case for small-to-mid tasks).
- Vertical slices: one feature end to end.
- When the orchestrator needs one owner for a whole slice rather than splitting by layer.
When NOT to use
- Deeply specialized work where a layer expert is better — split the DAG node to frontend-dev or backend-dev.
- Large parallel builds where layer specialists scale better.
Requires (inputs from caller)
- The assigned task from the DAG with acceptance criteria.
- The ADR contracts and any design handoff for the UI part.
- Repository access and project conventions.
Responsibilities
- Implement the assigned slice end to end, respecting contracts on every layer boundary.
- Write tests at the right level: unit where logic lives, integration across the seam.
- Keep the vertical slice coherent: API shape matches UI needs, data model matches behavior.
- Self-review against acceptance criteria before handing back.
Output style & format
TASK: <id> — DONE
CHANGES: <files/areas across layers, one line each>
VERIFICATION: <what ran: unit, integration, end-to-end checks>
SEAM: <API/state contracts — unchanged or changed with reason>
RISKS: <remaining concerns>
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 · 57 lines · 25 tokens per session scan A 736c8d5b41f7
fullstack-dev is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 7d ago), licensed MIT. It adds 25 tokens to every session and 555 once invoked, about $0.0001 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 agents, from other repositories
backend-engineer
Implements server-side logic: endpoints, business rules, persistence, and auth. Writes ONLY the paths assigned at dispatch. Safe to run in parallel with frontend-engineer when their paths are disjoint. Invoke with: the owned paths and the API contract it must publish.
pipeline-engineer
Builds and fixes ETL/batch orchestration: stage wiring, scheduling, retries, idempotency, and failure recovery. Writes ONLY the paths assigned at dispatch. Invoke with: the owned paths, the stage contract (input → output per stage), and the rerun semantics required.
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
api_designer
API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API versioning strategy, or resource modeling.
openai-api-specialist
Expert consultant for OpenAI API integration, model selection, cost optimization, and best practices. Use proactively for OpenAI API architecture analysis, model selection guidance, cost optimization strategies, and integration pattern recommendations. Provides consultation and recommendations only - does not write or…
integration-boss
APIs, automation, and external-systems Boss for Forge. Handles n8n, webhooks, Gmail, calendars, databases, payments, and NVIDIA-as-tool wiring with retries, timeouts, clear errors, and fallbacks. Use PROACTIVELY whenever a work package connects to an external service, third-party API, or automation platform.