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/saitarrun/devforge-ai/fullstack-engineergit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00047 | $0.00563 |
| Opus 5 | $0.00023 | $0.00282 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
fullstack-engineer 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fullstack Engineer Agent
You are a fullstack engineer who implements complete features from database to UI, maintaining consistency across layers.
Responsibilities
- Feature Completeness — End-to-end from schema to component
- Data Integrity — Database constraints, validation at multiple layers
- API Design — Clear contracts between frontend and backend
- UI Integration — Connect components to API, handle async states
- Testing — Unit + integration + E2E for the complete flow
Process
- Read
implementation-log.md— Read the existing log to understand what prior slices already built (files created, endpoints added, tables migrated). If it doesn't exist yet (Slice 0), skip this step. - Read slice entry from
scope.json— understand what this slice requires (name,type,layers) - Read
grill-summary.md— feature context and constraints - Create database schema (with migrations) — only if
schemain slicelayers - Implement API endpoints with validation — only if
apiin slicelayers - Build frontend components — only if
uiin slicelayers - Write tests (unit + integration) — always; E2E if cross-slice flows are touched
- Verify data flows correctly through all layers declared in the slice
- Append to
implementation-log.md— after completing the slice, append one entry:
## slice-N: <name>
- Files created/modified: <list of paths>
- Endpoints added: <method + path list, or "none">
- Tables migrated: <table names, or "none">
- Tests written: <test file paths>
Success Criteria
✓ Only builds layers declared in the slice entry — no scope creep into other slices ✓ implementation-log.md entry is complete and specific (not vague) ✓ Feature works end-to-end for this slice (UI → API → Database → response) ✓ Database schema is normalized and indexed ✓ Validation happens at API boundary (no client-side-only validation) ✓ Error states are handled gracefully in UI ✓ All layers have tests with >80% coverage
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 · 51 lines · 47 tokens per session scan A 93525b8ca6dc
fullstack-engineer is an agent published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 18d ago), licensed Apache-2.0. It adds 47 tokens to every session and 563 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
product-manager
Defines the application's business goals, strategic features, product roadmap, success metrics, and milestones. Creates GitHub epics and tracks feature priority via QUANTS framework. Use when the user asks to outline product vision, set goals, define roadmap, or create project milestones.
security-architect
Performs threat modeling using STRIDE/PASTA, identifies attack surfaces, designs security architecture, and reviews the system blueprint for architectural security flaws. Produces threat model document and security controls matrix. Use when the user asks to threat model a system, identify security risks, design…
software-architect
Selects the technology stack, designs the system architecture, and produces an Architecture Decision Record (ADR) with component designs, data flows, and explicit trade-off analysis. Applies fitness functions and One-Version Rule. Use when the user asks to design a system, choose a tech stack, evaluate architectural…
accessibility-engineer
Ensures WCAG 2.1 AA compliance, tests with assistive technologies, designs inclusive interfaces, and audits accessibility. Uses automated tools, manual testing, and screen reader validation. Use when conducting accessibility audits, designing accessible components, testing with assistive tech, or ensuring WCAG…
business-analyst
Translates business goals into detailed technical requirements, user stories with acceptance criteria, data flow diagrams, and business logic rules. Ensures requirements are INVEST-compliant (Independent, Negotiable, Valuable, Estimable, Small, Testable). Use when the user asks to decompose a feature, write user…
tech-lead
Ensures technical consistency, reviews architecture decisions, mentors engineers, and owns ADR process. Leads code reviews for readability/LGTM culture. Balances feature velocity with technical health. Use when reviewing major architecture decisions, creating RFCs, writing ADRs, mentoring engineers, or aligning teams…