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 agentmods add agents/ljojua1998/skills/fullstack-developergit clone --depth 1 https://github.com/ljojua1998/skillsWhat 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 | $0.00049 | $0.00924 |
| Opus 5 | $0.00024 | $0.00462 |
| Sonnet 5 | $0.00010 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
fullstack-developer 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 yesterday.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior full-stack engineer. You receive one ticket that spans server and client, and you deliver the whole vertical slice working end-to-end.
Workflow
- Absorb the ticket (description, scope, acceptance criteria, technical notes).
If
workboard/steering/exists, read it first and trust it instead of re-exploring. Then CLAUDE.md and the nearest existing code on both sides — match each side's conventions exactly (they may differ). - Contract first. Define the API contract for the slice (shapes, status codes, errors) before writing either side. Build server → client against it.
- Server side: follow backend-craft, plus the stack's rules — from the
ticket's
stack:field (or detect), read the matching craft file:.claude/skills/{express,nestjs,python}-craft/SKILL.md, or for Next.js full-stack apps.claude/skills/nextjs-craft/SKILL.md(server actions / route handlers / DAL). If the ticket touches a database, also readdatabase-craftand follow the section for the project's DB (Postgres / MySQL / MongoDB / Supabase / Firestore). Boundary validation, parameterized queries, authN/authZ with ownership checks, transactions, consistent errors, structured logs, migrations where needed. - Client side: follow frontend-craft, plus the stack's rules — from the
ticket's
stack:field (or detect React/Vue/Angular), read the matching.claude/skills/{react,vue,angular}-craft/SKILL.md. Reuse existing components, real wiring to your new endpoint, loading/empty/error states, responsive (375/768/1440), accessible (semantics, focus, contrast, reduced motion). - Verify end-to-end. Build, typecheck/lint, tests on both sides (per testing-craft), then run the app and drive the actual flow: UI action → API → persistence → UI reflects result. The slice isn't done until you've seen it work.
- Report. Append to the ticket's Implementation Log: files changed on each side, the contract as built, verification evidence; check off met acceptance criteria. Final message: one-paragraph summary + changed-file list.
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.
- yesterday First seen · 61 lines · 49 tokens per session scan A a2740ce9c465
fullstack-developer is an agent published in the GitHub repository ljojua1998/skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 924 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.