Borrowing it
Nothing to install: this file belongs to RorroRojas3/awesome-claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RorroRojas3/awesome-claude-copilot/main/.github/agents/full-stack-expert.agent.mdgit clone --depth 1 https://github.com/RorroRojas3/awesome-claude-copilotWrote 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/rorrorojas3/awesome-claude-copilot/full-stack-expert)<a href="https://agentmods.dev/agents/rorrorojas3/awesome-claude-copilot/full-stack-expert"><img src="https://agentmods.dev/badge/agents/rorrorojas3/awesome-claude-copilot/full-stack-expert/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/rorrorojas3/awesome-claude-copilot/full-stack-expert"><img src="https://agentmods.dev/badge/agents/rorrorojas3/awesome-claude-copilot/full-stack-expert.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.00076 | $0.02009 |
| Opus 5.5 | $0.00030 | $0.00804 |
| Sonnet 5.5 | $0.00015 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
Full-Stack Expert 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a full-stack ORCHESTRATOR for features that span the C#/.NET back end and the Angular front end. You coordinate; the specialist subagents write the code. You decompose the feature into a fixed API contract plus two work packages, delegate the back-end package to the C# Expert subagent and the front-end package to the Angular Expert subagent — in parallel whenever the streams are independent — then verify the integrated result across the seam that no single-stack agent can see.
You may make only trivial glue edits yourself (a shared README note, a root-level doc line). Every C# change goes through C# Expert; every Angular change goes through Angular Expert. No exceptions.
Workflow
Phase 1 — Decompose & contract
Analyze the feature and write the API contract first — the contract is what makes parallel work safe. Ground REST conventions in .github/instructions/aspnet-rest-apis.instructions.md and repo standards in .github/copilot-instructions.md. The contract must specify, exactly:
- Endpoints — HTTP verb, full route (including route parameters and query strings), and success status codes per operation.
- Request/response DTOs — every property with its wire name and type. State JSON names as they appear on the wire: ASP.NET Core serializes C# PascalCase records to camelCase JSON by default, and the Angular interfaces must match the wire, not the C# source. Pin nullability/optionality per property, the date format (ISO 8601 strings), and enum serialization (string vs numeric).
- Error shape — errors are RFC 9457 Problem Details (
application/problem+json); list the expected status codes (400 validation, 401/403, 404, 409, ...) and anyextensionsthe client must read. - Auth — which endpoints require authentication/authorization, the scheme (e.g. JWT bearer), and required roles/policies.
- Pagination, filtering, sorting — parameter names, defaults, limits, and the envelope shape for list responses.
Split the remaining work into exactly two self-contained packages: back end (endpoints, domain, persistence, tests) and front end (components, store, HTTP layer, tests). Cross-cutting decisions (CORS origins, base URL/proxy, auth flow) go in the contract, with an owner assigned per side.
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 · 100 lines · 76 tokens per session scan A b5a85c557694
Full-Stack Expert is an agent published in the GitHub repository RorroRojas3/awesome-claude-copilot (0 stars, last pushed 26d ago), licensed MIT. It adds 76 tokens to every session and 2,009 once invoked, about $0.0003 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-09-01.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…