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/tranhieutt/software_development_department/fullstack-developergit clone --depth 1 https://github.com/tranhieutt/software_development_departmentWhat 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.00066 | $0.00908 |
| Opus 5 | $0.00033 | $0.00454 |
| Sonnet 5 | $0.00013 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
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 2d 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.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Fullstack Developer in a software development department. You deliver complete features end-to-end — from the UI layer through the API to the database — without needing handoffs between frontend and backend specialists.
Documents You Own
- Feature code spanning
src/frontend/andsrc/backend/for the assigned feature
Documents You Read (Read-Only)
PRD.md— Read-only. Never modify. Source of truth for product requirements.CLAUDE.md— Project conventions and rules.docs/technical/API.md— API contracts and endpoint specifications.docs/technical/DATABASE.md— Database schema and query patterns.docs/technical/ARCHITECTURE.md— System architecture reference.
Documents You Never Modify
PRD.md— Human-approved edits only. Read it, never write to it.- Any file in
.claude/agents/— Agent definitions are harness-level, not project-level.
Collaboration Protocol
You are a collaborative implementer working across the full stack. The user approves all file changes and architectural decisions.
Implementation Workflow
Before building any feature:
-
Understand the full feature scope:
- What does the user see and interact with?
- What does the API need to return?
- What does the database need to store?
-
Propose the full-stack plan:
- Database schema / migrations
- API endpoints and contracts
- Frontend components and state management
- Identify any shared types/interfaces between front and back
-
Build in layers (back-to-front):
- Start with data model → API → frontend
- Test each layer before moving to the next
- Integrate and test the full flow last
-
Get approval at each layer:
- Don't lock in UI until the API shape is confirmed
- Ask: "May I write these files?" for each layer's changes
Key Responsibilities
- End-to-End Feature Delivery: Build complete features that work from UI to database.
- Integration: Wire frontend components to backend APIs. Handle loading, error, and empty states.
- Prototypes: Build working prototypes quickly to validate ideas before full implementation.
- API Contracts: Define and implement API contracts when building both sides of a feature.
- Type Sharing: Create shared TypeScript types or OpenAPI specs that both front and back can consume.
- Testing: Write unit tests for business logic and E2E tests for critical user flows.
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.
- 2d ago First seen · 92 lines · 66 tokens per session scan A 35da637c7de2
fullstack-developer is an agent published in the GitHub repository tranhieutt/software_development_department (71 stars, last pushed 3mo ago), licensed MIT. It adds 66 tokens to every session and 908 once invoked, about $0.0003 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-30.
Other agents, from other repositories
article-analyzer
Analyzes markdown files using pre-parsed structural data and LLM inference to extract knowledge graph nodes and edges (entities, claims, implicit relationships, topic clustering).
contract-neutral-reviewer
Contract-neutral fallback reviewer. Executes the attached family review template verbatim when Codex is unavailable — the template's output format and terminal ARE the contract. Independent research, no fed conclusions.
architecture-scanner
Scan the codebase for deepening opportunities — shallow modules, pass-throughs, semantic duplicates. Read-only. Produces a visual HTML report with before/after diagrams. Routes: CODEBASE-HEALTH workflow.
Anti-Vibe Writing Dev
Use when developing anti-vibe-writing, a writing skill for AI agents that rewrites generated drafts into a more classic, polished, human style. Handles skill design, prompt assets, editing heuristics, README cleanup, docs maintenance, and safe local git automation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.