Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ofoxai/skillsnpx agentmods add skills/ofoxai/skills/trellis-startWrote 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/ofoxai/skills/trellis-start)<a href="https://agentmods.dev/skills/ofoxai/skills/trellis-start"><img src="https://agentmods.dev/badge/skills/ofoxai/skills/trellis-start/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/ofoxai/skills/trellis-start"><img src="https://agentmods.dev/badge/skills/ofoxai/skills/trellis-start.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.00073 | $0.00619 |
| Opus 5.5 | $0.00029 | $0.00248 |
| Sonnet 5.5 | $0.00015 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
trellis-start 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 26d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Session
Initialize a Trellis-managed development session. This platform has no session-start hook, so manually load the equivalent context by following these steps (each one mirrors a section the hook would otherwise inject).
Step 1: Current state
Identity, git status, current task, active tasks, journal location.
python3 ./.trellis/scripts/get_context.py
If this output includes a line beginning Trellis update available:, copy the full line verbatim when summarizing session context. Do not shorten operational command hints.
Step 2: Workflow overview
Phase Index + skill routing table + DO-NOT-skip rules.
python3 ./.trellis/scripts/get_context.py --mode phase
Full guide in .trellis/workflow.md (read on demand).
Step 3: Guideline indexes
Discover packages + spec layers, then read each relevant index file.
python3 ./.trellis/scripts/get_context.py --mode packages
cat .trellis/spec/guides/index.md
cat .trellis/spec/<package>/<layer>/index.md # for each relevant layer
Index files list the specific guideline docs to read when you actually start coding.
Step 4: Decide next action
From Step 1 you know the current task. Check the task directory:
- Active task +
prd.mdexists → Phase 2 step 2.1. Load the step detail:python3 ./.trellis/scripts/get_context.py --mode phase --step 2.1 --platform codex - Active task + no
prd.md→ Phase 1.1. Load thetrellis-brainstormskill. - No active task → when the user describes multi-step work, load the
trellis-brainstormskill to clarify requirements, then create a task viatask.py create. For simple one-off questions or trivial edits, skip this and just answer directly — no task needed.
Skill routing (quick reference)
| User intent | Skill |
|---|---|
| New feature / unclear requirements | trellis-brainstorm |
| About to write code | trellis-before-dev |
| Done coding / quality check | trellis-check |
| Stuck / fixed same bug multiple times | trellis-break-loop |
| Learned something worth capturing | trellis-update-spec |
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.
- 26d ago First seen · 66 lines · 73 tokens per session scan A 0122e76b87f4
trellis-start is a skill published in the GitHub repository ofoxai/skills (2 stars, last pushed 27d ago), licensed MIT. It adds 73 tokens to every session and 619 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-09-23.
Other skills, from other repositories
autonomous-workflow
The phase-based machinery (0–7) behind the aw dispatcher — task intake through tested PR delivery in an isolated Git worktree, with optional companion skills for planning, quality gates, TDD, UX, code quality, docs, and CI verification. Companions never block; a skipped one is reported, never silent. NOT the entry…
to-issues-clearly
Create GitHub issues from a plan, bug, finding, audit or PRD, whose titles and bodies a stranger can act on. Use when filing issues or turning work into issue-sized slices. Routes unresolved decisions to a plain-language Question/Why/Questions/Done when shape; writes each issue in its verifier's language as Outcome…
implementer-mode
Implement a job handed over by a conductor: work inside the brief's scope and settled decisions, commit and push your own verified work, ask the conductor only for decisions you cannot make, file collisions and release blockers, open the PR without merging, and report per acceptance criterion in the PR body. Use when…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…