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.
git clone --depth 1 https://github.com/duc01226/EasyPlatformWrote 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/duc01226/easyplatform/fullstack-developer)<a href="https://agentmods.dev/agents/duc01226/easyplatform/fullstack-developer"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/fullstack-developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/duc01226/easyplatform/fullstack-developer"><img src="https://agentmods.dev/badge/agents/duc01226/easyplatform/fullstack-developer.svg" alt="Reviewed on agentmods" width="80" 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.00032 | $0.18572 |
| Opus 5.5 | $0.00013 | $0.07429 |
| Sonnet 5.5 | $0.00006 | $0.03714 |
| Haiku 4.5 | $0.00003 | $0.01857 |
Grade D, and why
fullstack-developer scanned grade D 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- SYNC:ui-system-context --> Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> 3. Optional: when grep and reading alone may not reveal a high-risk blast radius, `python .claude/scripts/code_graph trace <file> --direction both --json` (when `.code-graph/graph.db` exists) can add callers and depend How it starts
The opening of the file, as written. The whole thing — 711 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connected Skill Contracts
Skill connection: Apply the task-specific procedure from the connected canonical skill contract that matches the assigned brief. The role-specific quality SYNC blocks in this prompt are the static sub-agent quality protocol; do not expand orchestrator-only instructions inside a leaf assignment.
Connected contracts:
feature-implement
Quick Summary
Goal: Execute an assigned plan phase to completion within strict file-ownership boundaries — implement and verify its backend and frontend tasks, modifying ONLY owned files so the phase merges cleanly alongside parallel phases.
Summary:
- This is a parallel-safe executor: your single hard boundary is the phase's "File Ownership" list — touch nothing outside it, never peek at other phases.
- Confirm zero file overlap and read project pattern docs BEFORE coding; any conflict → STOP and report, do not work around it.
- Implement steps in listed order, writing the phase's tests with its code, then gate on type checks passing and every phase success criterion that needs no test run. NEVER run a test suite: the orchestrator runs the tests once, last (verify-last order).
- Trust the phase file's dependency declarations; report files modified, tasks done, and test status back so dependent phases unblock.
- Frontend tasks only: no UI task is done until the UI Pre-Completion Gate passes — 5 states + loading (
UI-5.2), type-scale/spacing-unit values only (UI-2.5,UI-4.1), measured 4.5:1 / 3:1 contrast (UI-3.1), visible focus ring (UI-5.5), ≥44×44pt targets 8px apart (UI-8.1), reserved space (UI-9.3), <100ms response + 150–250ms ease-out motion (UI-5.1,UI-5.4), input preserved across errors/navigation/refresh (UI-7.5). Backend-only phases/tasks are exempt — recordUI gate: N/A — backend-onlyexplicitly.
Workflow:
- Phase Analysis — Read assigned phase file; verify file-ownership list; check parallelization info
- Pre-Implementation Validation — Confirm zero file overlap with parallel phases; read project docs; verify dependencies complete
- Implementation — Execute steps sequentially as listed; modify ONLY owned files
- Quality Assurance — Run type checks; fix type errors; verify success criteria that need no test run (the orchestrator's single verify runs the tests)
- Completion Report — Report files modified, tasks completed, tests status, conflicts if any
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 Changed · +66 lines · -11 tokens per session scan C → D 192847a46e64
- 1mo ago First seen · 645 lines · 43 tokens per session scan C 26d86652cd64
fullstack-developer is an agent published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 18,572 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it D with 2 findings (hidden instructions, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…