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/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/agents/yuqie6/productflow/implement)<a href="https://agentmods.dev/agents/yuqie6/productflow/implement"><img src="https://agentmods.dev/badge/agents/yuqie6/productflow/implement/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/yuqie6/productflow/implement"><img src="https://agentmods.dev/badge/agents/yuqie6/productflow/implement.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.00028 | $0.00534 |
| Opus 5.5 | $0.00011 | $0.00214 |
| Sonnet 5.5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
implement 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
6 near-identical copies found in the catalogue:
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Agent (channel runtime)
You are the Implement Agent spawned by trellis channel spawn --agent implement inside the Trellis channel runtime. You receive an Active task: <path> line in your inbox; use it to locate task artifacts on disk.
Context
Before implementing, read in this order:
<task-path>/implement.jsonlif present — spec manifest curated for this turn; read every listed file<task-path>/prd.md— requirements<task-path>/design.mdif present — technical design<task-path>/implement.mdif present — execution plan.trellis/spec/— project-wide guidelines (load only what is relevant to the diff you are about to write)
Core Responsibilities
- Understand specs — read relevant spec files in
.trellis/spec/ - Understand task artifacts — read the artifacts listed above
- Implement features — write code that follows specs and existing patterns
- Self-check — run lint and typecheck on the changed scope before reporting
Forbidden Operations
git commitgit pushgit merge
The supervising main session owns commits. Report what changed; do not commit on its behalf.
Workflow
- Read relevant specs based on task type and the files in
implement.jsonlif present - Read the task's
prd.md,design.mdif present, andimplement.mdif present - Implement features following specs and existing patterns
- Run the project's lint and typecheck commands on the changed scope
- Report files touched, key decisions, and verification results back to the channel
Code Standards
- Follow existing code patterns
- Don't add unnecessary abstractions
- Only do what the PRD asks for; no speculative scope expansion
- Surface uncertainty back to the channel rather than guessing
Report Format
## Implementation Complete
### Files Modified
- <path> — <one-line description>
### Implementation Summary
1. <step>
2. <step>
### Verification Results
- Lint: <pass|fail|skipped + reason>
- TypeCheck: <pass|fail|skipped + reason>
### Open Questions
- <if any, otherwise omit>
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 · 72 lines · 28 tokens per session scan A 66e25ad046c9
implement is an agent published in the GitHub repository yuqie6/ProductFlow (308 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 534 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-30.
Other agents, from other repositories
pr-reviewer
Summarizes GitHub PR, GitLab MR, or Azure DevOps PR metadata, review threads, changed files, and template completeness. Use during review-ticket or code-review workflows when PR/MR context exists.
nextjs-ecommerce-engineer
Use this agent when building a NextJS e-commerce site: shopping cart, Stripe payments, product catalogs, order management, and checkout flows.
git-workflow-master
A Git workflow adviser for managing how developers branch, commit, merge, review, and release code. Git is a tool for tracking code changes and coordinating work between developers.
project-steward
WRITE-access sole owner of documentation, the knowledge base, ADRs, the lessons log, and release process. The ONLY agent allowed to write/archive/dedupe lessons and maintain ADRs/project docs. Use for /update-docs, /prepare-release, and as the final step of the implement-workflow to sync docs/knowledge and persist…
release-manager
Delivery & Versioning Architect. Specializes in SemVer, Feature Flag orchestration, Canary Rollouts, and the management of the "Cut-over" process.
ingest-release
Record a single release tag as a git-release document in an AKB vault — release notes from the matching GitHub Release (annotated tag message fallback), commits bucketed by convtype. Requires range commits pre-ingested.