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-spec-bootstrap/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-spec-bootstrap)<a href="https://agentmods.dev/skills/yuqie6/productflow/trellis-spec-bootstrap"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-spec-bootstrap/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-spec-bootstrap"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-spec-bootstrap.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.00067 | $0.00546 |
| Opus 5 | $0.00034 | $0.00273 |
| Sonnet 5 | $0.00013 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
trellis-spec-bootstrap 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 9d 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-spec-bootstrap — 100% identical, 0 lines differ
- trellis-spec-bootstrap — 100% identical, 0 lines differ
- trellis-spec-bootstrap — 100% identical, 0 lines differ
- trellis-spec-bootstrap — 100% identical, 0 lines differ
- trellis-spec-bootstarp — 92% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trellis Spec Bootstrap
Use this skill to create or refresh .trellis/spec/ guidelines from the real codebase. One capable agent owns the full loop: analyze the repository, choose the spec boundaries, write the docs, and verify the result. The workflow does not depend on a specific host, CLI, or agent brand.
Workflow
- Confirm Trellis is initialized and inspect the current
.trellis/spec/tree. - Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads.
- Decompose the spec work by package and layer only when that reflects the actual codebase.
- Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project.
- Verify that the final specs are internally consistent and contain no template placeholders.
Reference Routing
| Need | Read |
|---|---|
| Repository architecture analysis | references/repository-analysis.md |
| Spec work decomposition and task planning | references/spec-task-planning.md |
| Writing high-signal Trellis spec files | references/spec-writing.md |
| GitNexus and ABCoder MCP setup | references/mcp-setup.md |
Operating Rules
- Treat templates as starting points, not contracts. Delete, rename, split, or add spec files when the repository calls for it.
- Prefer source-backed rules over generic advice. Every important recommendation should point at a real file or repeated local pattern.
- Keep execution single-owner by default. Optional helper agents are an implementation detail, not a requirement or user-visible dependency.
- Do not write platform-specific instructions unless the target project already standardizes on that platform.
- Do not leave placeholder text, empty headings, or copied boilerplate in
.trellis/spec/.
Done Criteria
.trellis/spec/describes the project as it exists now.- Each relevant package or layer has practical coding guidance with real examples.
- Non-applicable template sections are removed.
index.mdfiles match the final spec file set.- Any required setup or analysis assumptions are documented in the relevant spec or task notes.
What ships with it
4 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.
- 9d ago First seen · 42 lines · 67 tokens per session scan A 97bfa68c06ce
trellis-spec-bootstrap is a skill published in the GitHub repository yuqie6/ProductFlow (302 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 546 once invoked, about $0.0003 per session on Opus 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
spec-generate
Product Spec Builder that helps PMs generate clear, structured, testable PRDs. Creates both full and lightweight specs for any product or platform with a guided step-by-step workflow. Output in English Markdown format.
dev-todo-mode
A task-execution format for software requests received through Telegram. It presents a short plan, reports progress after each stage, and ends with changed files and verification results.
telegram-announce
Purpose.
notion
Notion API for creating and managing pages, databases, and blocks.
bear-notes
Create, search, and manage Bear notes via grizzly CLI.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.