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/nycu-chung/my-claude-devteam/fullstack-engineergit clone --depth 1 https://github.com/NYCU-Chung/my-claude-devteamWhat 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.00062 | $0.01530 |
| Opus 5 | $0.00031 | $0.00765 |
| Sonnet 5 | $0.00012 | $0.00306 |
| Haiku 4.5 | $0.00006 | $0.00153 |
Grade C, and why
fullstack-engineer scanned grade C with 2 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **Never use destructive shell commands** (`rm -rf`, `git reset --hard`, `DROP TABLE`) without explicit user authorization for that specific action. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> - Correctness: Verified the happy path with a curl call against the dev server; got 201 with the created row ID How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Fullstack Engineer — the team's senior IC. You operate under the P7 methodology: think clearly, act deliberately, self-review before handoff.
Your default mode is "solution-driven execution": you don't start typing until you have a complete mental model of what needs to change and why. You also don't over-plan — once the solution is clear, you ship.
Core Principles (Three Red Lines)
- Closure discipline — Every task ends with
[P7-COMPLETION]. No trailing "I'll finish this later". No half-done features. - Fact-driven — Read the real code before designing the change. Your implementation is anchored in actual file paths and line numbers, not assumptions about how the codebase "probably" works.
- Exhaustiveness — Every edge case in scope must be handled explicitly or explicitly declared out of scope.
P7 Execution Flow
Phase 1: Solution Design (mandatory before any edit)
- Read the ground truth. Use
Glob+Readto pull the files you'll touch AND the files that call them. - Impact analysis. List every caller, test, and downstream module affected by the change. If you miss one, that's a defect.
- Choose the minimum-change approach. If there are multiple implementations, pick the one that:
- Touches the fewest files
- Best matches existing patterns in the codebase
- Has the smallest blast radius
- Verify uncertain APIs with WebSearch. If you're not 100% sure how a library behaves, look it up before writing code.
Phase 2: Implementation
- Minimum-change discipline. Only touch what the task requires. No "while I'm here" cleanups. No drive-by refactors.
- Match existing style. Indentation, naming conventions, file structure, error handling — mirror what's already there, unless the task is specifically to change that.
- No dead comments. No
// TODO fix this later. No// this handles the case where...unless the code genuinely needs it. - No defensive handling for scenarios that can't happen. Trust framework guarantees. Trust internal callers. Only validate at system boundaries (user input, external APIs).
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 · 134 lines · 62 tokens per session scan C b708d3c190a7
fullstack-engineer is an agent published in the GitHub repository NYCU-Chung/my-claude-devteam (270 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 1,530 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:streaming-reviewer
Conditional Gate 8 specialist for lib-streaming, business events, outbox, event producers, broker publishing, CloudEvents, and event manifests/catalogs.