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 skills add LuizEduPP/Rememb --skill subagent-driven-developmentgit clone --depth 1 https://github.com/LuizEduPP/RemembWrote 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/skills/luizedupp/rememb/subagent-driven-development)<a href="https://agentmods.dev/skills/luizedupp/rememb/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/subagent-driven-development/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/skills/luizedupp/rememb/subagent-driven-development"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/subagent-driven-development.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.00034 | $0.00834 |
| Opus 5.5 | $0.00014 | $0.00334 |
| Sonnet 5.5 | $0.00007 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
subagent-driven-development 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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subagent-Driven Development
Overview
Use this skill to execute a written implementation plan through isolated workers with explicit review gates. If the current environment supports subagents, use them. If it does not, use the closest equivalent isolated-task workflow while keeping the same control pattern.
When to Use
Use this skill when:
- a plan already exists
- tasks are mostly independent
- you want to preserve coordinator context while delegating implementation
- you want spec compliance and code quality checked separately
Prefer a simpler inline workflow when tasks are tightly coupled or when the environment cannot isolate task execution meaningfully.
Core Workflow
- Read the implementation plan once and extract the full text for each task.
- Create a tracking list for all tasks before dispatching workers.
- For each task, dispatch one isolated implementer worker with the full task text and required context.
- If the implementer requests clarification, answer it before implementation continues.
- After implementation, run a spec-compliance review.
- Only after spec compliance passes, run a code-quality review.
- If either review finds issues, return the task to the implementer and repeat the relevant review.
- Mark the task complete only when both reviews pass.
- After all tasks are complete, run one final end-to-end review and verification pass.
Inputs / Assumptions
- The plan is already written and broken into actionable tasks.
- Each worker receives the task text directly rather than discovering it indirectly.
- The coordinator keeps authority for sequencing, context, and approval.
- Isolation matters more than raw speed for this workflow.
Worker Status Model
Implementers should report one of these statuses:
DONE: implementation completed and ready for reviewDONE_WITH_CONCERNS: implementation completed, but there are correctness or scope concerns to inspect firstNEEDS_CONTEXT: missing information blocks safe completionBLOCKED: the task cannot proceed under current assumptions or current worker capability
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 117 lines · 34 tokens per session scan A e33f229c584e
subagent-driven-development is a skill published in the GitHub repository LuizEduPP/Rememb (5 stars, last pushed 12d ago), licensed MIT. It adds 34 tokens to every session and 834 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
web-artifacts-builder
Suite of tools for creating elaborate, multi-component Prismer HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
document-actions
Extract cited facts, obligations, deadlines and proposed actions from documents, preserving OCR uncertainty and reconciling Prismer tasks.
webapp-qa
Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.