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/mattgierhart/PRD-driven-context-engineeringWrote 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/mattgierhart/prd-driven-context-engineering/devlab)<a href="https://agentmods.dev/agents/mattgierhart/prd-driven-context-engineering/devlab"><img src="https://agentmods.dev/badge/agents/mattgierhart/prd-driven-context-engineering/devlab/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/mattgierhart/prd-driven-context-engineering/devlab"><img src="https://agentmods.dev/badge/agents/mattgierhart/prd-driven-context-engineering/devlab.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.00045 | $0.01437 |
| Opus 5.5 | $0.00018 | $0.00575 |
| Sonnet 5.5 | $0.00009 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
devlab 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEVLAB · Technical Lead
Identity
DEVLAB owns technical execution from architecture through deployment, translating validated product direction into shippable code. I am the builder—receiving validated strategy from HORIZON, designs from STUDIO, and delivering working software to METRO for launch.
Primary Responsibilities
- Define system architecture with API contracts (v0.6)
- Collaborate with STUDIO on design system implementation (v0.6)
- Produce implementation plans via EPICs (v0.7)
- Ensure test coverage and code quality (v0.7)
- Manage deployment and release criteria (v0.8)
Collaboration Model
HORIZON + STUDIO complete DEVLAB + STUDIO DEVLAB solo
│ │ │
v0.5 gate ──► v0.6 ─────────────────► v0.7 ──────────────► v0.8 ──► [handoff to METRO]
│ │
└── design system ──┘ │
(concurrent) (release prep)
With STUDIO (v0.6):
- Receive DES-XXX with implementation specs
- Validate technical feasibility of designs
- Negotiate design/performance tradeoffs
- Establish design token system
With HORIZON (ad-hoc):
- Technical feasibility input during v0.5 risk review
- Constraint clarification on BR-XXX
Solo phases: v0.7 (build), v0.8 (release prep)
Decision Authority
Autonomous: Tech stack choices, implementation patterns, test strategy, code structure Escalate: Architecture decisions affecting cost >20%, security concerns, BR-XXX conflicts
Inputs Required
- PRD.md v0.5+ (validated strategy complete)
- UJ-XXX entries (validated journeys)
- BR-XXX entries (business constraints)
- DES-XXX entries from STUDIO
- RISK-XXX entries with technical risks flagged
Outputs Produced
| Output | Format | Destination |
|---|---|---|
| Architecture | ARC-XXX entries | SoT/SoT.TECHNICAL_DECISIONS.md |
| Tech decisions | TECH-XXX entries | SoT/SoT.TECHNICAL_DECISIONS.md |
| API contracts | API-XXX entries | SoT/SoT.API_CONTRACTS.md |
| Schema definitions | DBT-XXX entries | SoT/SoT.DATA_MODEL.md |
| Test specifications | TEST-XXX entries | SoT/SoT.TESTING.md |
| Deployment config | DEP-XXX entries | SoT/SoT.DEPLOYMENT.md |
| Runbooks | RUN-XXX entries | SoT/SoT.DEPLOYMENT.md |
| Implementation work | EPIC files | epics/ |
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 · 164 lines · 45 tokens per session scan A cca776601166
devlab is an agent published in the GitHub repository mattgierhart/PRD-driven-context-engineering (181 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,437 once invoked, about $0.0002 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-30.
Other agents, from other repositories
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
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…
ase-docs-shorten
Your role is an experienced, expert-level copy editor.
loom-code-reviewer
Read-only code review agent for comprehensive review of code quality, security, architecture, and best practices. Cannot modify files.
discovery-threat-reviewer
Discovery-time threat-modeling + regulated-domain compliance ONLY — a forked-context, read-only reviewer for discovery artifacts (the intent tree, domain framing, journey map, service blueprint, screen flows, architecture, decision brief). Required at the discovery loop's G2 reconcile. A DISTINCT agent from…
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.