Borrowing it
Nothing to install: this file belongs to lxyer/multi-agent-collaboration-system. 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/lxyer/multi-agent-collaboration-system/main/.agents/skills/integrate-skill/SKILL.mdgit clone --depth 1 https://github.com/lxyer/multi-agent-collaboration-systemWrote 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/lxyer/multi-agent-collaboration-system/integrate-skill)<a href="https://agentmods.dev/skills/lxyer/multi-agent-collaboration-system/integrate-skill"><img src="https://agentmods.dev/badge/skills/lxyer/multi-agent-collaboration-system/integrate-skill.svg" alt="Measured on agentmods" 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.00071 | $0.01507 |
| Opus 5 | $0.00036 | $0.00754 |
| Sonnet 5 | $0.00014 | $0.00301 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
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 7d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrate Skill into Project Guidelines
Adapt and integrate a reusable skill into your project's development guidelines (not directly into project code).
Usage
$integrate-skill <skill-name>
Examples:
$integrate-skill frontend-design
$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
Locate and read the skill instructions:
.agents/skills/<skill-name>/SKILL.mdin the repository- Skill list in
AGENTS.md(when available in current context)
If the skill cannot be found, ask the user for the source path or repository.
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.
- 7d ago First seen · 222 lines · 71 tokens per session scan A 2d4da52f3f09
integrate-skill is a skill published in the GitHub repository lxyer/multi-agent-collaboration-system (1 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,507 once invoked, about $0.0004 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-31.
Other skills, from other repositories
meta-cognition-parallel
An experimental tool for analysing a question or problem in parallel across three layers.
rust-learner
Use when asking about Rust versions or crate info. Keywords: latest version, what's new, changelog, Rust 1.x, Rust release, stable, nightly, crate info, crates.io, lib.rs, docs.rs, API documentation, crate features, dependencies, which crate, what version, Rust edition, edition 2021, edition 2024, cargo add, cargo…
rust-router
A routing skill for Rust development questions, including errors, design choices, comparisons, and coding tasks involving Rust tools and packages.
m07-concurrency
A guide to running work at the same time in Rust, either on threads or through async tasks. It covers shared data, channels, locks, atomics, futures, and common problems such as races and deadlocks.
m14-mental-model
Use when learning Rust concepts. Keywords: mental model, how to think about ownership, understanding borrow checker, visualizing memory layout, analogy, misconception, explaining ownership, why does Rust, help me understand, confused about, learning Rust, explain like I'm, ELI5, intuition for, coming from Java, coming…
rust-call-graph
A visualisation tool for Rust function call graphs, showing which functions call one another.