Borrowing it
Nothing to install: this file belongs to yuqie6/ProductFlow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yuqie6/ProductFlow/main/.agents/skills/trellis-before-dev/SKILL.mdgit clone --depth 1 https://github.com/yuqie6/ProductFlowWrote 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/yuqie6/productflow/trellis-before-dev)<a href="https://agentmods.dev/skills/yuqie6/productflow/trellis-before-dev"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-before-dev/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/yuqie6/productflow/trellis-before-dev"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-before-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.00415 |
| Opus 5.5 | $0.00028 | $0.00166 |
| Sonnet 5.5 | $0.00014 | $0.00083 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
trellis-before-dev 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- trellis-before-dev — 100% identical, 2 lines differ
- trellis-before-dev — 100% identical, 2 lines differ
- trellis-before-dev — 97% identical, 13 lines differ
- trellis-before-dev — 91% identical, 20 lines differ
- before-dev — 89% identical, 20 lines differ
What it actually says
Read the relevant development guidelines before starting your task.
Execute these steps:
-
Read current task artifacts:
prd.mdfor requirements and acceptance criteriadesign.mdif present for technical designimplement.mdif present for execution order and validation plan
-
Discover packages and their spec layers:
python3 ./.trellis/scripts/get_context.py --mode packages -
Identify which specs apply to your task based on:
- Which package you're modifying (e.g.,
cli/,docs-site/) - What type of work (backend, frontend, unit-test, docs, etc.)
- Any spec/research paths referenced by the task artifacts
- Which package you're modifying (e.g.,
-
Read the spec index for each relevant module:
cat .trellis/spec/<package>/<layer>/index.mdFollow the "Pre-Development Checklist" section in the index.
-
Read the specific guideline files listed in the Pre-Development Checklist that are relevant to your task. The index is NOT the goal — it points you to the actual guideline files (e.g.,
error-handling.md,conventions.md,mock-strategies.md). Read those files to understand the coding standards and patterns. -
Always read shared guides:
cat .trellis/spec/guides/index.md -
Understand the coding standards and patterns you need to follow, then proceed with your development plan.
This step is mandatory before writing any code.
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 · 41 lines · 70 tokens per session scan A 859894f2e825
trellis-before-dev is a skill published in the GitHub repository yuqie6/ProductFlow (307 stars, last pushed 18d ago), licensed MIT. It adds 70 tokens to every session and 415 once invoked, about $0.0003 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 skills, from other repositories
ordercli
Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).
resume-builder
Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON…
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
stripe-skill
Process payments, manage customers, issue refunds, and handle subscriptions via the Stripe CLI. Pass any Stripe command (customers, charges, paymentintents, refunds, invoices, products, prices, subscriptions) and the tool runs it for you and returns parsed JSON.
dodo-payments-skill
Take payments and manage billing in Dodo Payments through its official SDK — look up payments, subscriptions, customers, products, refunds and disputes, send checkout and customer-portal links, refund payments, cancel subscriptions, change plans, and call any other Dodo API endpoint. Output is Dodo's own JSON.
stripe-payments
Add Stripe payments to a web app — Checkout Sessions, Payment Intents, subscriptions, webhooks, customer portal, and pricing pages. Covers the decision of which Stripe API to use, produces working integration code, and handles webhook verification. No MCP server needed — uses Stripe npm package directly. Triggers…