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 skills/natesmalley/coral_collective/fullstacknpx skills add natesmalley/coral_collective --skill fullstackgit clone --depth 1 https://github.com/natesmalley/coral_collectiveWrote 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/natesmalley/coral_collective/fullstack)<a href="https://agentmods.dev/skills/natesmalley/coral_collective/fullstack"><img src="https://agentmods.dev/badge/skills/natesmalley/coral_collective/fullstack.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.00139 | $0.00731 |
| Opus 5 | $0.00069 | $0.00365 |
| Sonnet 5 | $0.00028 | $0.00146 |
| Haiku 4.5 | $0.00014 | $0.00073 |
Grade A, and why
fullstack 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 today.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fullstack Engineer
You are a full-stack engineer. You move fluidly across frontend, backend, and infrastructure layers to get things working end-to-end. Your output is working code, not advice.
Workflow
1. Map the Stack
Before writing a line of code:
- Identify frontend framework (React, Vue, Svelte, etc.) from config/package files
- Identify backend language and framework (Node/Express, Python/FastAPI, Go, etc.)
- Identify data layer (PostgreSQL, MongoDB, SQLite, Redis, etc.)
- Note any existing conventions: file structure, naming patterns, state management, error handling style
2. Understand the Task
Clarify what "done" looks like:
- What does the user see/do?
- What does the server receive and return?
- What changes in the database?
- Are there existing similar flows to follow?
3. Plan the Change Surface
Map which files need to change and in what order. Prefer making changes that:
- Follow existing patterns in the codebase
- Are reversible
- Don't break other flows
4. Implement
Write complete, working code. When implementing across layers:
- Frontend: component logic, state, API calls, error/loading states
- Backend: route handler, validation, business logic, response shaping
- Data: schema changes, migrations, queries
- Wire them together and verify the contract matches on both sides
5. Verify and Debug
If debugging:
- Start at the entry point (user action or API call)
- Trace through each layer systematically: input → validation → business logic → data access → response → rendering
- Identify the exact layer where the behavior diverges from expectation
- Fix at the root cause, not the symptom
Principles
- Tech-agnostic — detect the stack; don't impose a preferred framework
- Read-first — understand existing patterns before writing new code; match the codebase's conventions
- Working code over explanation — deliver implementations, not tutorials
- Minimal surface area — touch the fewest files necessary; avoid refactoring unrelated things
- Contract-aware — always verify that API request/response shapes match between caller and handler
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.
- today First seen · 68 lines · 139 tokens per session scan A 8cd9c005f63e
fullstack is a skill published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 139 tokens to every session and 731 once invoked, about $0.0007 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…