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 HK-hub/AgentSkills --skill fullstack-devgit clone --depth 1 https://github.com/HK-hub/AgentSkillsWrote 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/hk-hub/agentskills/fullstack-dev)<a href="https://agentmods.dev/skills/hk-hub/agentskills/fullstack-dev"><img src="https://agentmods.dev/badge/skills/hk-hub/agentskills/fullstack-dev.svg" alt="Measured on agentmods" 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.00133 | $0.08435 |
| Opus 5 | $0.00067 | $0.04217 |
| Sonnet 5 | $0.00027 | $0.01687 |
| Haiku 4.5 | $0.00013 | $0.00843 |
Grade A, and why
fullstack-dev scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3000/health This is a copy
100% identical to fullstack-dev — 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 — 1,038 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full-Stack Development Practices
MANDATORY WORKFLOW — Follow These Steps In Order
When this skill is triggered, you MUST follow this workflow before writing any code.
Step 0: Gather Requirements
Before scaffolding anything, ask the user to clarify (or infer from context):
- Stack: Language/framework for backend and frontend (e.g., Express + React, Django + Vue, Go + HTMX)
- Service type: API-only, full-stack monolith, or microservice?
- Database: SQL (PostgreSQL, SQLite, MySQL) or NoSQL (MongoDB, Redis)?
- Integration: REST, GraphQL, tRPC, or gRPC?
- Real-time: Needed? If yes — SSE, WebSocket, or polling?
- Auth: Needed? If yes — JWT, session, OAuth, or third-party (Clerk, Auth.js)?
If the user has already specified these in their request, skip asking and proceed.
Step 1: Architectural Decisions
Based on requirements, make and state these decisions before coding:
| Decision | Options | Reference |
|---|---|---|
| Project structure | Feature-first (recommended) vs layer-first | Section 1 |
| API client approach | Typed fetch / React Query / tRPC / OpenAPI codegen | Section 5 |
| Auth strategy | JWT + refresh / session / third-party | Section 6 |
| Real-time method | Polling / SSE / WebSocket | Section 11 |
| Error handling | Typed error hierarchy + global handler | Section 3 |
Briefly explain each choice (1 sentence per decision).
Step 2: Scaffold with Checklist
Use the appropriate checklist below. Ensure ALL checked items are implemented — do not skip any.
Step 3: Implement Following Patterns
Write code following the patterns in this document. Reference specific sections as you implement each part.
Step 4: Test & Verify
After implementation, run these checks before claiming completion:
- Build check: Ensure both backend and frontend compile without errors
# Backend cd server && npm run build # Frontend cd client && npm run build - Start & smoke test: Start the server, verify key endpoints return expected responses
# Start server, then test curl http://localhost:3000/health curl http://localhost:3000/api/<resource> - Integration check: Verify frontend can connect to backend (CORS, API base URL, auth flow)
- Real-time check (if applicable): Open two browser tabs, verify changes sync
What ships with it
8 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.
- 3d ago First seen · 1,038 lines · 133 tokens per session scan A 94d2f5b38596
fullstack-dev is a skill published in the GitHub repository HK-hub/AgentSkills (6 stars, last pushed 20d ago), licensed MIT. It adds 133 tokens to every session and 8,435 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to fullstack-dev, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
add-tauri-command
Use when adding a new Tauri command to Cowork-Z — a new backend capability the React frontend must call, a new #[tauri::command] fn, or a new invoke() wrapper in tauri-api.ts. Also use when a newly written command returns "Command not found" at runtime.
prd-to-app
Build a complete, production-ready full-stack web application from PRD documents, prototype images, and resource files. Handles the entire pipeline: system design, database schema, seed data, backend API, frontend UI, visual verification against prototypes, and deployment script generation. Use this skill whenever the…
web-development
Architect, build, debug, review, optimize, and ship production websites, web apps, APIs, plugins, themes, and integrations across WordPress, WooCommerce, Elementor, React, Next.js, Node.js, TypeScript, databases, caching, deployment, SEO, accessibility, performance, and build tooling. Use for any implementation…
searchpo-agent-capabilities
Use when Searchpo agents need to inspect available .env keys, provider/API capabilities, DeepWiki MCP availability, credential routing, side-effect boundaries, or decide which agent should use which external service without exposing secrets.
search-harness
Domain knowledge for designing a search harness for coding agents — search API landscape, ground-API pipeline/strategy, CLI + skills architecture, and roadmap. Use when discussing search agent infrastructure, choosing search APIs for agents, designing search pipelines, or reviewing the search-harness project direction.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.