Borrowing it
Nothing to install: this file belongs to lie5860/openai-search-mcp. 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/lie5860/openai-search-mcp/main/.cursor/commands/trellis-integrate-skill.mdgit clone --depth 1 https://github.com/lie5860/openai-search-mcpWrote 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/commands/lie5860/openai-search-mcp/trellis-integrate-skill)<a href="https://agentmods.dev/commands/lie5860/openai-search-mcp/trellis-integrate-skill"><img src="https://agentmods.dev/badge/commands/lie5860/openai-search-mcp/trellis-integrate-skill/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/commands/lie5860/openai-search-mcp/trellis-integrate-skill"><img src="https://agentmods.dev/badge/commands/lie5860/openai-search-mcp/trellis-integrate-skill.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.00000 | $0.01429 |
| Opus 5 | $0.00000 | $0.00714 |
| Sonnet 5 | $0.00000 | $0.00286 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
trellis-integrate-skill 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 11d 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.
This is a copy
100% identical to integrate-skill — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate Claude Skill into Project Guidelines
Adapt and integrate a Claude global skill into your project's development guidelines (not directly into project code).
Usage
/trellis-integrate-skill <skill-name>
Examples:
/trellis-integrate-skill frontend-design
/trellis-integrate-skill mcp-builder
Core Principle
[!] Important: The goal of skill integration is to update development guidelines, not to generate project code directly.
- Guidelines content -> Write to
.trellis/spec/{target}/doc.md- Code examples -> Place in
.trellis/spec/{target}/examples/skills/<skill-name>/- Example files -> Use
.templatesuffix (e.g.,component.tsx.template) to avoid IDE errorsWhere
{target}isfrontendorbackend, determined by skill type.
Execution Steps
1. Read Skill Content
openskills read <skill-name>
If the skill doesn't exist, prompt user to check available skills:
# Available skills are listed in AGENTS.md under <available_skills>
2. Determine Integration Target
Based on skill type, determine which guidelines to update:
| Skill Category | Integration Target |
|---|---|
UI/Frontend (frontend-design, web-artifacts-builder) |
.trellis/spec/frontend/ |
Backend/API (mcp-builder) |
.trellis/spec/backend/ |
Documentation (doc-coauthoring, docx, pdf) |
.trellis/ or create dedicated guidelines |
Testing (webapp-testing) |
.trellis/spec/frontend/ (E2E) |
3. Analyze Skill Content
Extract from the skill:
- Core concepts: How the skill works and key concepts
- Best practices: Recommended approaches
- Code patterns: Reusable code templates
- Caveats: Common issues and solutions
4. Execute Integration
4.1 Update Guidelines Document
Add a new section to the corresponding doc.md:
@@@section:skill-<skill-name>
## # <Skill Name> Integration Guide
### Overview
[Core functionality and use cases of the skill]
### Project Adaptation
[How to use this skill in the current project]
### Usage Steps
1. [Step 1]
2. [Step 2]
### Caveats
- [Project-specific constraints]
- [Differences from default behavior]
### Reference Examples
See `examples/skills/<skill-name>/`
@@@/section:skill-<skill-name>
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.
- 11d ago First seen · 220 lines · 0 tokens per session scan A bb15144c3089
trellis-integrate-skill is a command published in the GitHub repository lie5860/openai-search-mcp (13 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,429 tokens. A static security scan graded it A with 0 findings. It is 100% identical to integrate-skill, differing in 8 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.