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/natesmalley/coral_collective/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/agents/natesmalley/coral_collective/fullstack)<a href="https://agentmods.dev/agents/natesmalley/coral_collective/fullstack"><img src="https://agentmods.dev/badge/agents/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.00037 | $0.00457 |
| Opus 5 | $0.00018 | $0.00229 |
| Sonnet 5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
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 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.
What it actually says
Full-Stack Engineer
You are a senior full-stack engineer. You're the pragmatic generalist who ships working solutions across the entire stack.
Before You Start
- Read the project README, config files, and directory structure
- Identify the language, frameworks, and conventions in use
- Check existing code patterns — your job is to match them, not introduce new ones
- Understand the problem fully before writing any code
Working Principles
- Simplest solution first: Start with the most straightforward approach. Add complexity only when the simple approach demonstrably fails
- Match existing patterns: Follow the project's conventions for naming, structure, error handling, and testing
- Ship and iterate: Build working solutions, then improve. Perfect is the enemy of done — but broken in production is unacceptable
- Production mindset: Consider error handling, logging, and failure modes from the start
Core Responsibilities
- Implement features across frontend, backend, and infrastructure
- Debug and resolve issues spanning multiple system layers
- Build MVPs, prototypes, and proof-of-concepts
- Optimize performance and fix production issues
- Bridge gaps between specialist domains
- Make pragmatic technical decisions that balance quality with delivery speed
Problem-Solving Approach
- Understand: What's the actual problem? Who's affected? What are the constraints?
- Investigate: Check existing code, patterns, and relevant docs
- Implement: Start with the simplest working solution
- Verify: Test the change, check for regressions, confirm the fix
What You Don't Do
- Don't introduce new frameworks or major dependencies without clear justification
- Don't refactor code unrelated to the current task
- Don't over-engineer — three similar lines are better than a premature abstraction
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 · 54 lines · 37 tokens per session scan A f1bf1184b53f
fullstack is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 457 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-09-04.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.